"Extraction of image from host ###### failed. Failed to extract image from the host: no stored copy available for inactive VIB VMware_locker_tools-light_####"
On the vCenter Server, in /var/log/vmware/vmware-updatemgr/vum-server/vmware-vum-server.log:
YYYY-MM-DDTHH:MM:SSZ info vmware-vum-server[####] [Originator@6876 sub=Telemetry] [TelemetryManager 261] Sending telemetry data: {"@type":"taskId":"#######","entityId":"errorMessageId":"com.vmware.vcIntegrity.lifecycle.ExtractDepotTask.HostExtractDepotFailed;com.vmware.vcIntegrity.lifecycle.EsxImage.ReservedVibExtractError","errorMessage":"Extraction of image from host ###### failed.;Failed to extract image from the host: no stored copy available for inactive VIB VMware_locker_tools-light_##########.","errorTime":"YYYY-MM-DDTHH:MM:SSZ"}
YYYY-MM-DDTHH:MM:SSZ Er(11) lifecycle [#######] : HostSeeding:#### Extract depot failed: ('VMware_locker_tools-light_##########', 'tools', 'Calculated digest at EOF does not match expected result: b9e58f62509cabffc3c78dd29dcc69cf28bb1bf3808e5ae714ebd######## calculated, e616d8b7edc86f9c3a267368861b19222884d7e34fa75d977150238b######## expected.')VMware vSphere ESXi 8.x
esxcli software component remove -n VMware-VM-Tools
esxcli software component apply -d "</vmfs/volumes/datastore_name>"/VMware-ESXi-####-depot.zip -n VMware-VM-Tools
Alternate Method: Set Up a New Image Manually. See 'Option 3: Set Up a New Image Manually' in the following documentation.
Convert a Cluster or a Host That Uses Baselines Into a Cluster or a Host That Uses vSphere Lifecycle Manager Images
Note: Setting up the image manually forces the cluster to look at the "known good" metadata in the vSphere Lifecycle Manager depot rather than trying to validate and extract the specific VIBs currently residing on the ESXi host's local storage.