"Setting desired image spec for cluster failed" error during vSphere HA Configuration

Products

• VMware vCenter Server
• VMware vSphere ESXi

Issue/Introduction

• When attempting to configure or re-configure vSphere High Availability (HA) on an ESXi host post-vCenter Server upgrade, the operation fails with the errors:
  Cannot complete the configuration of the vSphere HA agent on the host. Setting desired image spec for cluster failed.
Cannot complete the configuration of the vSphere HA agent on the host. Applying HA VIBs on the cluster encountered a failure.
• Affected ESXi hosts remain in a "retrying" state under the vSphere HA configuration view.
• Management agents (hostd and vpxa) fail to report the correct status, and attempts to force an HA reconfiguration fail consistently.
• The /var/log/vmware/vpxd/vpxd.log in the vCenter Server reports recurring no_response errors for the affected ESXi host despite confirmed network connectivity.
• VMs are present in an 'invalid' state directly on the ESXi host, which are otherwise functional on other ESXi hosts in the vCenter Server.

Environment

VMware vCenter Server 8.0.x

Cause

• The failure is caused by a persistent state misalignment in the host management agents (hostd/vpxa) and stale VM metadata persisted on the ESXi host following the vCenter upgrade.
• This state misalignment prevents the vCenter Server from successfully pushing the desired image specification to the Fault Domain Manager (FDM) agent, resulting in the "Setting desired image spec for cluster failed" error.

Resolution

Perform the following host-level remediation to clear the stale agent states and metadata corruption.

1. Take a snapshot of the vCenter Server Appliance. Check the vCenter Server Snapshot KB article.
2. In the vSphere Client, right-click the affected ESXi host and select Maintenance Mode > Enter Maintenance Mode.
3. Migrate all running virtual machines to other hosts within the cluster.
   Note: If DRS is enabled and set to fully automated, DRS migrates all the running VMs off the host.
4. Confirm the host is fully in Maintenance Mode and no pending tasks are in a running state for the host.
5. Restart the ESXi host to clear the management agent cache and reset the local metadata.
6. Once the host reboots and reconnects to the vCenter Server, right-click the host and select Maintenance Mode > Exit Maintenance Mode.
7. Then check the status of vSphere HA for the affected host.

Additional Information

• If the issue persists, review /var/log/fdm-installer.log and /var/log/vpxa.log on the ESXi host for specific VIB installation failures or "invalid state" faults.
• For general vSphere HA troubleshooting, refer to Troubleshooting VMware High Availability (HA) issues in VMware vCenter Server.