HA status changed to uninitialized state on the ESXi hosts in the cluster after VC upgrade.
search cancel

HA status changed to uninitialized state on the ESXi hosts in the cluster after VC upgrade.

book

Article ID: 384443

calendar_today

Updated On:

Products

VMware vCenter Server 7.0 VMware vCenter Server 8.0

Issue/Introduction

  • After VC upgrade you see that HA status changed to uninitialized state on the ESXi hosts in the cluster.
  • In /var/log/vmware/vmware-updatemgr/vum-server/vmware-vum-server-xx.log,

    -Depot Sync task started

    yyyy-mm-ddThh:mm:ss.usZ info vmware-vum-server[4189873] [Originator@6876 sub=com.vmware.vcIntegrity.lifecycle.SyncDepotsTask] [Task, 524] Task:com.vmware.vcIntegrity.lifecycle.SyncDepotsTask ID:<taskID>. Task Created

    -HA offline bundle copy started
    yyyy-mm-ddThh:mm:ss.usZ info vmware-vum-server[4188607] [Originator@6876 sub=com.vmware.vcIntegrity.lifecycle.PreloadOfflineBundlesTask] [PreloadOfflineBundlesTask 112] Copying offline bundle from: /etc/vmware-vpx/docRoot/vSphere-HA-depot/vsphere-ha-depot.zip to: /storage/updatemgr/patch-store-temp/vsphere-ha-depot.zip
    yyyy-mm-ddThh:mm:ss.usZ info vmware-vum-server[4188607] [Originator@6876 sub=com.vmware.vcIntegrity.lifecycle.CreateOfflineDepotTask] [Task, 524] Task:com.vmware.vcIntegrity.lifecycle.CreateOfflineDepotTask ID<taskID> Task Created
    yyyy-mm-ddThh:mm:ss.usZ info vmware-vum-server[4189960] [Originator@6876 sub=ServiceProvider] [ImageService 372] Run command: --taskid <taskID> --threadid 4189960 depots --validate --depot /storage/updatemgr/patch-store-temp/vsphere-ha-depot.zip

     

    -HA offline bundle task finished
    yyyy-mm-ddThh:mm:ss.usZ info vmware-vum-server[4189960] [Originator@6876 sub=com.vmware.vcIntegrity.lifecycle.CreateOfflineDepotTask] [Task, 524] Task:com.vmware.vcIntegrity.lifecycle.CreateOfflineDepotTask ID:<taskID>. Task State updated to SUCCEEDED


    -Depot Sync Task finished
    yyyy-mm-ddThh:mm:ss.usZ info vmware-vum-server[4189980] [Originator@6876 sub=com.vmware.vcIntegrity.lifecycle.SyncDepotsTask] [Task, 524] Task:com.vmware.vcIntegrity.lifecycle.SyncDepotsTask ID:<taskID>. Task State updated to SUCCEEDED


    -HA setSolution task fails with below log signature in vmware-vum-server-xx.log file
    less vmware-vum-server-xx.log | grep -i "Originator@6876 sub=com.vmware.vcIntegrity.lifecycle.SetSolutionTask"

    yyyy-mm-ddThh:mm:ss.usZ info vmware-vum-server[4189981] [Originator@6876 sub=com.vmware.vcIntegrity.lifecycle.SetSolutionTask] [Task, 524] Task:com.vmware.vcIntegrity.lifecycle.SetSolutionTask ID:5217dfa7-dae1-413c-14fc-55282f72425b. Task Created
    yyyy-mm-ddThh:mm:ss.usZ info vmware-vum-server[4191164] [Originator@6876 sub=com.vmware.vcIntegrity.lifecycle.SetSolutionTask] [SetSolutionTask 155] Check depot for solution: com.vmware.vsphere-ha_8.0.3-24322831
    yyyy-mm-ddThh:mm:ss.usZ info vmware-vum-server[4191164] [Originator@6876 sub=com.vmware.vcIntegrity.lifecycle.SetSolutionTask] [SetSolutionTask 169] HA depot is not load yet
    yyyy-mm-ddThh:mm:ss.usZ error vmware-vum-server[4191164] [Originator@6876 sub=com.vmware.vcIntegrity.lifecycle.SetSolutionTask] [SetSolutionTask 184] Failed to set solution on domain-c1006. Reason: HA depot not loaded yet
    yyyy-mm-ddThh:mm:ss.usZ info vmware-vum-server[4191164] [Originator@6876 sub=com.vmware.vcIntegrity.lifecycle.SetSolutionTask] [Task, 524] Task:com.vmware.vcIntegrity.lifecycle.SetSolutionTask ID:5217dfa7-dae1-413c-14fc-55282f72425b. Finalizing Task
    yyyy-mm-ddThh:mm:ss.us info vmware-vum-server[4191164] [Originator@6876 sub=com.vmware.vcIntegrity.lifecycle.SetSolutionTask] [Task, 524] Task:com.vmware.vcIntegrity.lifecycle.SetSolutionTask ID:5217dfa7-dae1-413c-14fc-55282f72425b. Task Finalization completed.
    yyyy-mm-ddThh:mm:ss.usZ error vmware-vum-server[4191164] [Originator@6876 sub=com.vmware.vcIntegrity.lifecycle.SetSolutionTask] [Task, 524] Task:com.vmware.vcIntegrity.lifecycle.SetSolutionTask ID:5217dfa7-dae1-413c-14fc-55282f72425b. Task Failed. Error: Error:
    yyyy-mm-ddThh:mm:ss.usZ info vmware-vum-server[4191164] [Originator@6876 sub=com.vmware.vcIntegrity.lifecycle.SetSolutionTask] [Task, 524] Task:com.vmware.vcIntegrity.lifecycle.SetSolutionTask ID:5217dfa7-dae1-413c-14fc-55282f72425b. Task State updated to FAILED
    yyyy-mm-ddThh:mm:ss.usZ info vmware-vum-server[4189980] [Originator@6876 sub=com.vmware.vcIntegrity.lifecycle.SetSolutionTask] [Task, 524] Task:com.vmware.vcIntegrity.lifecycle.SetSolutionTask ID:527353c4-447c-88b7-3de6-f069ffb857cc. Task Created

Cause

Before VLCM comes online, the HA state changed to uninitialized state and HA keeps requesting to set solution with newer version and the set solution tasks were failing due to unavailability of HA depot. Because of this vLCM takes some time to sync the Online Depot and Offline depot which includes fdm and wcp.

Resolution

Do not disable and enable the HA cluster which  stops the sync depot task to complete. Allow the task to complete.

This is an expected behavior. After the VC is upgraded new version of FDM vibs is needed on the ESXi to properly configure HA as the depot that contains the new FDM vibs is needed to be loaded into vLCM. Right after VC upgrade there can be a delay in enabling/disabling/configuring the HA until the new depots are loaded.

The new depot needs to be loaded only once after VC upgrade. After the depot has been loaded the HA enable/disable will not see this kind of delay because of depot sync.

Powered by Wolken Software