vSphere Lifecycle Manager (vLCM) fails to scan or remediate ESXi hosts. This occurs when the Update Manager patch store contains corrupted or missing metadata files. Symptoms can include:
com.vmware.vcIntegrity.ScanFailed./var/log/vmware/vmware-updatemgr/vum-server/vmware-vum-server.log, you see:error vmware-vum-server[####] [Originator@6876 sub=HostUpdateDepotManager] Failed to get filesize for: /storage/updatemgr/patch-store/hostupdate/<VENDOR_DIRECTORY>/metadata_####.zip
Error: boost::filesystem::file_size: No such file or directory: "/storage/updatemgr/patch-store/hostupdate/<VENDOR_DIRECTORY>/metadata_####.zip"
Corrupted metadata artifacts in the Update Manager repository prevent the scanner from calculating file sizes and verifying patch availability.
To resolve this issue, you must reset the Update Manager database and purge the patch store to force a fresh synchronization.
Resetting the Update Manager database is a destructive task. Custom baselines (but not Cluster Images), custom download settings and manually imported patches/ISOs will be removed and will need to be reapplied following the reset.
service-control --stop vmware-updatemgrpython /usr/lib/vmware-updatemgr/bin/updatemgr-utility.py reset-dbrm -rf /storage/updatemgr/patch-store/*service-control --start vmware-updatemgrFor software downloads, see the Broadcom Support Portal. If the issue persists, contact Broadcom Support.