Re-enable HA on this cluster: Wait for HA enable failedResume Restart**, the task may fail again. /var/log/vmware/vmware-updatemgr/vum-server/vmware-vum-server.log` may show:A failure occurred when starting a host compliance check operation on host : Error: com.vmware.vapi.std.errors.not_allowed_in_current_stateMessages: com.vmware.esx.task.contention <Another task is in progress. Please retry later.>/var/run/log/lifecycle.log` may report:DepotCollection:### Downloading depot index.xml from http://<VC_FQDN>:9084/vum/repository/hostupdate/__micro-depot__vendor-vmw__metadata-13__index__.xmlDownloader:### Opening http://<VC_FQDN>:9084/vum/repository/hostupdate/__micro-depot__vendor-vmw__metadata-13__index__.xml for downloadDownloader:### Download failed: <urlopen error [Errno -3] Temporary failure in name resolution>, 9 retry left...Downloader:### Download failed: <urlopen error [Errno -3] Temporary failure in name resolution>, 8 retry left...Downloader:### Download failed: <urlopen error [Errno -3] Temporary failure in name resolution>, 7 retry left...Downloader:### Download failed: <urlopen error [Errno -3] Temporary failure in name resolution>, 6 retry left...Downloader:### Download failed: <urlopen error [Errno -3] Temporary failure in name resolution>, 5 retry left...Downloader:### Download failed: <urlopen error [Errno -3] Temporary failure in name resolution>, 4 retry left...Downloader:### Download failed: <urlopen error [Errno -3] Temporary failure in name resolution>, 3 retry left...Downloader:### Download failed: <urlopen error [Errno -3] Temporary failure in name resolution>, 2 retry left...Downloader:### Download failed: <urlopen error [Errno -3] Temporary failure in name resolution>, 1 retry left...DepotCollection:### Could not download from depot at http://<VC_FQDN>:9084/vum/repository/hostupdate/__micro-depot__vendor-vmw__metadata-13__index__.xml, skipping (('http://<VC_FQDN>:9084/vum/repository/hostupdate/__micro-depot__vendor-vmw__metadata-13__index__.xml', '', '<urlopen error [Errno -3] Temporary failure in name resolution>'))task.contention` errors during subsequent retries.Ensure that DNS services are available and functioning before restarting the vSAN cluster.
Verify that ESXi hosts can resolve the vCenter FQDN.
nslookup <vCenter-FQDN>If DNS cannot be made available immediately, use one of the following workarounds on every ESXi host in the cluster:
Non-persistent workaround:
Add an entry directly to /etc/hosts. This change does not persist across ESXi host reboots.
<vCenter_IP_Address> <vCenter_FQDN>
Persistent workaround:
Use the following command to add a host entry that persists across ESXi host reboots:
esxcli network ip hosts add --hostname <VC_FQDN> --ip <VC_IP>If com.vmware.esx.task.contention errors persist, reboot the affected ESXi hosts to clear stale background tasks and release the lock.
Click Resume Restart or retry the operation in the vSphere Client.
Refer KB article: After enabling Lifecycle Manager and initiating a Compliance Check, vSphere HA fails
To speak with a customer representative or a Support Engineer see Contact Broadcom Support. Scroll to the bottom of the page and click on your respective region.