HA cannot be enabled on Image-Based clusters with the error: setting desired image spec for cluster failed

Products

• VMware vCenter Server

Issue/Introduction

• vSphere HA cannot be enabled on Image-Based clusters with the error: setting desired image spec for cluster failed WCP  service may fail to start.
• Enabling HA on other Clusters of the VCSA works just fine.
• Edit Image shows the error Failed to Serialize/Deserialize Object.

• Configuring HA in the VCSA will show the error Cannot complete the configuration of the vSphere HA agent on the Host.
• It can be related to the recent VCSA certificate replacement.
• You may also see error "image validation failed"
• In the /var/log/vmware/vmware-updatemgr/vum-server/vmware-vum-server.log on the vCenter, you may see entries similar to: vum-server$ less vmware-vum-server-123.log | grep Java
  YYYY-MM-DD HH:MM:SS info vmware-vum-server[50453] [Originator@6876 sub=managedJetty] [managedJetty 457] Jetty: Java Environment:
  YYYY-MM-DD HH:MM:SS info vmware-vum-server[51153] [Originator@6876 sub=DraftsManager] [DraftsManager 637] GetDesiredSoftwareInfo called for the entity: Cluster (domain-c12345)
  YYYY-MM-DD HH:MM:SS error vmware-vum-server[50564] [Originator@6876 sub=Clusters::Software::Reports::HardwareCompatibilitySvc] [AsyncServiceImpl 112] Failed to Get Compliance for cluster domain-c12345(Cluster). No record - VCIDB ERROR: Row with primary key domain-c12345 not found in table PM_HCL_COMPLIANCES
  YYYY-MM-DD HH:MM:SS info vmware-vum-server[51160] [Originator@6876 sub=DraftsManager] [DraftsManager 637] GetDesiredSoftwareInfo called for the entity: Cluster (domain-c12345)
  YYYY-MM-DD HH:MM:SS info vmware-vum-server[51159] [Originator@6876 sub=DraftsManager] [DraftsManager 788] ListDrafts called for the entity: Cluster (domain-c12345)
  YYYY-MM-DD HH:MM:SS info vmware-vum-server[51153] [Originator@6876 sub=DraftsManager] [DraftsManager 747] DeleteDraft called for the entity: Cluster (domain-c12345) by author: [e-mail]
  YYYY-MM-DD HH:MM:SS info vmware-vum-server[50458] [Originator@6876 sub=DraftsManager] [DraftsManager 637] GetDesiredSoftwareInfo called for the entity: Cluster (domain-c12345)
  YYYY-MM-DD HH:MM:SS error vmware-vum-server[50504] [Originator@6876 sub=Clusters::Software::Reports::HardwareCompatibilitySvc] [AsyncServiceImpl 112] Failed to Get Compliance for cluster domain-c12345(Cluster). No record - VCIDB ERROR: Row with primary key domain-c12345 not found in table PM_HCL_COMPLIANCES
  YYYY-MM-DD HH:MM:SS info vmware-vum-server[50504] [Originator@6876 sub=DraftsManager] [DraftsManager 692] CreateDraft called for the entity: Cluster (domain-c12345) by author: [e-mail]
  YYYY-MM-DD HH:MM:SS info vmware-vum-server[51158] [Originator@6876 sub=com.vmware.vcIntegrity.lifecycle.DraftValidateTask] [Task, 457] Task:com.vmware.vcIntegrity.lifecycle.DraftValidateTask ID:52242b90-bfd8-ead7-05c6-c095b86b0d43. Starting Validate Draft Task: user: [e-mail], draft_id: 60 for the entity: Cluster (domain-c12345)
  YYYY-MM-DD HH:MM:SS info vmware-vum-server[51154] [Originator@6876 sub=DraftsManager] [DraftsManager 637] GetDesiredSoftwareInfo called for the entity: Cluster (domain-c12345)
  YYYY-MM-DD HH:MM:SS error vmware-vum-server[51153] [Originator@6876 sub=Clusters::Software::Reports::HardwareCompatibilitySvc] [AsyncServiceImpl 112] Failed to Get Compliance for cluster domain-c12345(Cluster). No record - VCIDB ERROR: Row with primary key domain-c12345 not found in table PM_HCL_COMPLIANCES

 

Environment

VMware vCenter Server 8.x
VMware vCenter Server 7.x

Cause

Missing VIB.

Resolution

Follow these steps:

1. In the vcenter run the following command: 

   cd /storage/updatemgr/patch-store/hostupdate/vmw/vib20/vmware-fdm
   ls -ltrah

You will see just one or no VIB's for FDM. You may also see there are missing VIBs

2. Once you identify the missing VIB you could proceed to download the missing VIB from the attachments section of this KB.
3. Once downloaded proceed to upload the file to the affected VCSA and save it to path /storage/updatemgr/patch-store/hostupdate/vmw/vib20/vmware-fdm/
4. Restart vCenter services with command service-control --stop --all && service-control --start --all

Additional Information

Impact/Risks:
Medium, depending on the customer's need, it could prevent patching of ESXi hosts of a cluster.