Sync Updates for vShere Lifecycle Manager fails.
Attempting to sync updates with vSphere Lifecycle Manager generates an error similar to:
error vmware-vum-server[935269] [Originator@6876 sub=HostUpdateDepotManager] [patchDepotManager 482] Failed to get filesize for: /storage/updatemgr/patch-store/hostupdate/AVG/metadata-107.zip,
please check if the file exists and accessible. Error: boost::filesystem::file_size: No such file or directory [system:2]: "/storage/updatemgr/patch-store/host
update/AVG/metadata
In the journlctl.log file, you see entries similar to:
----------------------------------------------------------------------
MM DD Time vpxd[30061]: Event [211034924] [1-1] [YY-MM-DDT(Time)] [vim.event.ExtendedEvent] [warning] [] [Cluster_Name] [211032625] [Current progress of remediation: 0 hosts completed successfully, 0 hosts completed with errors, 1 hosts are being remediated, 0 hosts are waiting to start remediation, and 0 hosts could not enter maintenance mode and are waiting to retry.]
MM DD Time vpxd[30061]: Event [211046749] [1-1] [YY-MM-DDT(Time)] [vim.event.ExtendedEvent] [warning] [] [Cluster_Name] [211032625] [Current progress of remediation: 1 hosts completed successfully, 0 hosts completed with errors, 0 hosts are being remediated, 0 hosts are waiting to start remediation, and 0 hosts could not enter maintenance mode and are waiting to retry.]
MM DD Time vpxd[30061]: Event [211065663] [1-1] [YY-MM-DDT(Time)] [vim.event.ExtendedEvent] [warning] [] [Cluster_Name] [211064524] [Current progress of remediation: 0 hosts completed successfully, 0 hosts completed with errors, 1 hosts are being remediated, 0 hosts are waiting to start remediation, and 0 hosts could not enter maintenance mode and are waiting to retry.]
In the vum-server.log, you see entries similar to:
---------------------------------------------------------------------
[#47] YY-MM-DDT(Time) verbose vmware-vum-server[53394] [Originator@6876 sub=ComplianceStatusMgr] [complianceStatusMgr 1005] QueryEntityComplianceStatus called by client on entity:host-700164
[#47] YY-MM-DDT(Time) verbose vmware-vum-server[53394] [Originator@6876 sub=ComplianceStatusMgr] [vciUtilities 4078] get baselines for entity: host-700164
[#47] YY-MM-DDT(Time) verbose vmware-vum-server[53394] [Originator@6876 sub=ComplianceStatusMgr] [vciUtilities 4149] entity: host-700164 baselines: 1 , 2 , 40
[#47] --> entity = 'vim.HostSystem:e5578e52-9b7a-4fa0-9c03-7626ea7ad9ef:host-700164',
--> 'vim.HostSystem:e5578e52-9b7a-4fa0-9c03-7626ea7ad9ef:host-700164'
[#47] --> key = 'vim.HostSystem:e5578e52-9b7a-4fa0-9c03-7626ea7ad9ef:host-700164',
--> 'vim.HostSystem:e5578e52-9b7a-4fa0-9c03-7626ea7ad9ef:host-700164'
[#47] --> key = 'vim.HostSystem:e5578e52-9b7a-4fa0-9c03-7626ea7ad9ef:host-700164',
YY-MM-DDT(Time) info vmware-vum-server[53395] [Originator@6876 sub=InventoryTree] [InventoryTree 340] [AcquireWriteLock] Node host-700164 write locked successfully, new Lock state: Write.
YY-MM-DDT(Time) info vmware-vum-server[53395] [Originator@6876 sub=JobDispatcher] [JobDispatcher 2167] Scheduling task SingleHostScanTask{1551} that imposes 3 for ESX: host-700164 new load: 3 that imposes 2 for VMware vSphere Update Manager new load: 4
YY-MM-DDT(Time) info vmware-vum-server[54165] [Originator@6876 sub=scanHost20] [remediateHost 140] Create RemediateHost Host: host-700164 hostInMModeOnStart: 0 lastTask: 1
YY-MM-DDT(Time) error vmware-vum-server[54165] [Originator@6876 sub=VciClusterPrePatchScanTask.VciClusterPrePatchScanTask{1549}] [vciClusterPrePatchScanTask 213] Patch scan task failed for host : host-700164. This host will not be remediated
YY-MM-DDT(Time) info vmware-vum-server[53395] [Originator@6876 sub=JobDispatcher] [JobDispatcher 2258] Removing task SingleHostScanTask{1551} that imposed ESX load:3 for esx host-700164, new load: 0 that imposed VMware vSphere Update Manager load:2, new load: 2
Phase where it errors out:
-------------------------------------
YY-MM-DDT(Time) info vmware-vum-server[935269] [Originator@6876 sub=VUMConfig] [vumConfigImpl 125] Patch depot url: http://vCenter_fqdn:9084/vum/repository/
YY-MM-DDT(Time) error vmware-vum-server[935269] [Originator@6876 sub=HostUpdateDepotManager] [patchDepotManager 482] Failed to get filesize for: /storage/updatemgr/patch-store/hostupdate/AVG/metadata-107.zip, please check if the file exists and accessible. Error: boost::filesystem::file_size: No such file or directory [system:2]: "/storage/updatemgr/patch-store/host
update/AVG/metadata-107.zip"
YY-MM-DDT(Time) error vmware-vum-server[935269] [Originator@6876 sub=SingleHostScanTask.SingleHostScanTask{1586}] [vciTaskBase 728] Task execution has failed: boost::filesystem::file...
VMware vCenter Server Appliance 8.0.x
Reset VMware Update Manager Database.
---------------------------------------------------------
1. Power off all vCenters and take offline snapshots for linked mode), For stand-alone vCenter you can take powered on snapshot.
2. Access the vCenter Server via a PuTTY session and run the following commands:
service-control --stop vmware-updatemgr
python /usr/lib/vmware-updatemgr/bin/updatemgr-utility.py reset-db
rm -rf /storage/updatemgr/patch-store/*
service-control --start vmware-updatemgr