Error: Unsupported downgrade of manually added VMware Tools component during vLCM remediation in ESXi 9.1

Products

• VMware vCenter Server
• VMware Cloud Foundation

Issue/Introduction

• When performing image-based remediation in vSphere Lifecycle Manager (vLCM) on an ESXi 9.1 environment, the compliance check or remediation task fails. 

• The compliance check fails with the following error:
  
  "Version 13.1.0 of the manually added Component ESXi VM Tools is an unsupported downgrade from version 13.1.0 on the host. Replace the Component in the image with one of the same or higher version."



• The ESX hosts have the 13.1.0 tools VIB installed natively.

Environment

• VMware Cloud Foundation (VCF) 9.1

• ESXi 9.1.x

Cause

vSphere Lifecycle Manager (vLCM) image remediation does not proceed when the desired image downgrades manually added, OEM, or partner async components. This occurs when the ESXi host contains newer driver components or VIBs than the versions included in the desired vLCM image or vendor addon.

The desired image must contain matching or higher component versions, or the conflicting unused components must be removed or aligned before remediation.

Resolution

To resolve this issue, manually remove the component from the cluster's desired state by modifying the exported image configuration.

Important: In normal scenarios, components should not be removed from the cluster image. This workaround is specific to "Patch update" scenarios where the ESXi host natively already contains the required VMware Tools VIB (13.1.0), and the manually added component in the vLCM image is causing a redundant conflict.

1. Navigate to Cluster > Updates > Image.

2. Select the option to Export the image configuration as a JSON file.

3. Open the JSON file in a text editor and locate the Components section.

   Example JSON:

   {
    "add_on": null,
    "alternative_images": null,
    "base_image": {
        "version": "9.1.0.0.25370933"
    },
    "components": {
        "VMware-VM-Tools": "13.1.0-0.25370933"
    },
    "hardware_support": null,
    "removed_components": null,
    "solutions": null
}

4. Remove the entry corresponding to the manually added VMware Tools or ESXi VM Tools component.

   "components": {

       },

5. Save the JSON file.

6. In the vSphere Client, select Import and upload the modified JSON file.

7. Run the Check Compliance scan again. The error should no longer appear, and remediation can proceed.

Additional Information

• Contact Broadcom support