In this scenario, the host is running a newer build (e.g., 8.0 U3g – 24859861), while the Cluster Image is configured with an older build (e.g., 8.0 U3e – 24674464).
This error occurs because the ESXi host was upgraded outside of the Cluster Image lifecycle, typically by using an ISO. vSphere Lifecycle Manager is designed to maintain a "desired state" and prevents the downgrade of base images or components to ensure system stability.
Because the host version is now ahead of the cluster's defined image, vLCM marks the host as incompatible until the cluster's desired state is updated to match or exceed the version currently running on the host.
To resolve version mismatches between hosts and the cluster configuration in vSphere Lifecycle Manager (vLCM), update the Cluster Image definition to match the software already running on the hardware.
Using an Offline Bundle (.zip) is the best practice here, as standard ISOs often lack the metadata required for vLCM to populate the version dropdown menus correctly.
1.Import Bundle Offline
The Offline Bundle contains the metadata necessary for vLCM to recognize the build as a valid "Base Image."
Download: Obtain the relevant ESXi Offline Bundle (.zip) from the Broadcom Support Portal.
Import: In the vSphere Client, navigate to Lifecycle Manager > Image Depot > Import Updates.
Upload: Select and upload the .zip file.
Note: Always prioritize the
.zipformat over the.isowhen managing the Image Depot to ensure all component metadata is correctly indexed.
2. Align the Cluster Image, manually point the cluster definition to this specific version.
Edit Image: Navigate to Cluster > Updates > Image > Edit.
Select Versions:
ESXi Version: Select the desired version (e.g., 8.0 Update 3g - 24859861).
Vendor Add-on: Select the corresponding vendor-specific package (e.g., HPE Customization or Dell Add-on).
Save: Click Validate to ensure compatibility, then click Save.
Compliance Check: Run Check Compliance.
If the software version in the Image definition now matches the version physically installed on the hosts, the status will change to Compliant. Because the versions are identical, no remediation or reboot will be required.