vSphere HA Configuration Fails via vLCM with Error "Image is not valid"
search cancel

vSphere HA Configuration Fails via vLCM with Error "Image is not valid"

book

Article ID: 444224

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

 

  • When attempting to enable vSphere High Availability (HA) at the cluster level, the configuration task fails.

  • The configuration task aborts with the following explicit validation errors in the vSphere Client:

    • "Image is not valid."

    • "No compatible Component vSphere FDM is found in Solution vSphere HA, candidate versions are: VCSA build number."

  • This issue occurs because the cluster's vSphere Lifecycle Manager (vLCM) desired image metadata cache drifts out of sync.

  • The orchestration layer continues to track an older, legacy ESXi  image structure.

  • A critical software mismatch is created when the vCenter Server (vSphere 9.x) management layer attempts to inject the modern vSphere Fault Domain Manager (FDM) 9.0 component into the obsolete host image baseline template.Attempts to inject the modern vSphere Fault Domain Manager (FDM) 9.0 component into the obsolete host image baseline template.



Environment

 

  • vCenter Server Appliance (VCSA) 9.x

  • VMware ESXi 8.x / 7.x

  • vSphere Lifecycle Manager (vLCM) Image-Based Clusters

 

 

Cause

 

  • When vSphere HA is enabled, vCenter Server pushes and installs the corresponding Fault Domain Manager (FDM) agent binaries onto the ESXi hosts within the cluster.

  • The cluster's vLCM desired state metadata template is mismatched, incorrectly pointing to an ESXi legacy image base configuration.

  • vLCM cannot calculate a valid software transition path due to this metadata mismatch.

  • It fails to find an FDM agent version that is simultaneously compatible with both a vSphere 9.x management layer and the legacy ESXi , causing the vLCM validation check to abort the deployment.

 

 

Resolution

The issue was caused by an inconsistency between the cluster's desired image configuration maintained by vSphere Lifecycle Manager (vLCM) and the actual ESXi version running on the hosts. As a result, vSphere HA was unable to deploy or validate the required FDM agents.

To resolve the issue, perform the following steps:
1. Update the Cluster Desired Image

  • Log in to the vSphere Client.
  • Select the affected cluster from the inventory.
  • Navigate to Updates > Image under the vSphere Lifecycle Manager (vLCM) section.
  • Click Edit to modify the cluster image specification.

2. Align the ESXi Base Image Version

  • Review the ESXi version currently installed on the cluster hosts.
  • Update the ESXi Base Image in the desired image configuration to match the exact ESXi release running on the hosts (for example, ESXi 8.0 Update 3f).
  • Save the configuration changes.

Note: Saving the updated image forces vLCM to regenerate the desired-state metadata and refresh the image definition cache.
3. Validate Cluster Compliance

  • From the Image tab, select Check Compliance.
  • Verify that the cluster image validates successfully and no image-definition errors are reported.

4. Re-enable vSphere HA

  • Navigate to Cluster > Configure > vSphere Availability.
  • Click Edit.
  • Enable vSphere HA and apply the changes.


Once the image definition has been corrected and validated, vSphere HA successfully deploys the Fault Domain Manager (FDM) agents to all hosts, and the cluster exits the HA configuration error state.

Result
After updating the desired image to match the installed ESXi release and re-enabling vSphere HA, the FDM agent installation completes successfully and the cluster reports a healthy HA configuration status.

Powered by Wolken Software