"Host is not compatible with the image" error during vSphere Lifecycle Manager (vLCM) remediation of NSX-prepared clusters

Products

• VMware NSX

Issue/Introduction

When performing an NSX upgrade or host remediation within a vSphere Lifecycle Manager (vLCM) enabled cluster, the compliance check or remediation task fails with the error: "Host is not compatible with the image." This typically occurs because the host contains component versions (such as Vendor Addons or specific VIBs) that are newer than what is defined in the cluster's Desired Image, triggering vLCM downgrade protection.

Environment

• VMware Cloud Foundation (VCF) / Standalone vSphere
• VMware NSX 4.x
• VMware vCenter Server 7.x / 8.x
• vSphere Lifecycle Manager (vLCM) enabled clusters

Cause

The vLCM remediation process prevents downgrading software components already installed on the hardware. If a host was manually updated or contains a newer Vendor Addon version than the cluster's defined image, vLCM will flag the host as incompatible. During NSX upgrades, this can manifest if the NSX VIBs fail to uninstall/update correctly, leaving stale or mismatched versions on the host.

Resolution

To resolve this issue, align the cluster's desired image with the host's software state using one of the following methods:

Method 1: Update the Cluster Image

1. Navigate to the vSphere Client > Cluster > Updates > Image.
2. Select Edit on the cluster image.
3. Update the Vendor Addon or specific Components to a version that matches or exceeds the version currently installed on the host hardware.
4. Run a Check Compliance and proceed with Remediate All.

Method 2: Manual Host Cleanup (Use if Method 1 is not feasible)

1. Place the affected host in Maintenance Mode.
2. Move the host out of the vLCM cluster to the Datacenter root folder.
3. In the NSX UI (System > Fabric > Hosts), select the host and perform a Delete NSX (use Force Delete if it shows as "Orphaned").
4. SSH into the ESXi host and verify NSX VIBs: esxcli software vib list | grep nsx.
5. If VIBs remain, stop the proxy and remove them:
   • /etc/init.d/nsx-proxy stop
   • nsxcli -c del nsx
6. Reboot the ESXi host.
7. Verify VIBs are removed, then move the host back into the vLCM cluster to allow automatic re-preparation.