vLCM compliance shows "The operation cannot continue due to downgrade of the following Components: [component name]." when changing hardware vendor custom images

Products

• VMware vSphere ESXi

Issue/Introduction

When migrating an ESXi host or cluster from one hardware vendor's custom image deployment to a different hardware vendor's custom baseline, vSphere Lifecycle Manager (vLCM) may block remediation. The image compliance check reports that it considers the action to be a "downgrade" for the ESX version or specific components, preventing the update from moving forward.

Environment

VMware vCenter Server

VMware ESX

vSphere Lifecycle Manager

Cause

This behavior is expected within vSphere Lifecycle Manager (vLCM). The system is designed to prevent the automated "downgrade" of drivers or components already installed on your hosts to ensure system stability. Because the hosts currently have vendor-specific components that have higher version numbers than those in the target custom image, vLCM blocks the execution

Resolution

To resolve the compliance block, the conflicting VIBs from the previous vendor must be manually uninstalled via the CLI:

1. Log into the vSphere Client and navigate to the affected cluster.

2. Select the host, right-click, and choose Maintenance Mode > Enter Maintenance Mode.

3. Navigate to Updates > Image > Image Compliance and note the exact names of the components flagged as a "Downgrade."

4. Connect to the ESXi host via SSH using root credentials.

5. Remove the flagged components by running the following command:

   esxcli software vib remove -n <component-name>

   
   Note: Substitute <component-name> with the exact name noted in Step 3.

6. Restart the ESXi host if prompted by the command output.

7. Return to the vSphere Client, select the cluster, and click Check Compliance.

8. Once the compliance status updates to clear the downgrade block, click Remediate to apply the new vendor image.

9. Exit Maintenance Mode.