Error: "Downgrades of host VIBs <name>(<version>) in the image are not supported" when attempting to update ESXi hosts with vLCM
search cancel

Error: "Downgrades of host VIBs <name>(<version>) in the image are not supported" when attempting to update ESXi hosts with vLCM

book

Article ID: 394653

calendar_today

Updated On:

Products

VMware vSphere ESXi VMware Cloud Foundation

Issue/Introduction

When attempting to update ESXi hosts with vLCM using the single image option, the following similar messages appear when reviewing Image Compliance:

  • The "Check Compliance" status for the ESXi host returns "Incompatible" on vLCM.
  • When attempting to remediate or check compliance of an ESXi host against a vSphere Lifecycle Manager (vLCM) cluster image, the process fails with errors:

    Downgrades of host VIBs <name>(<version>) in the image are not supported.
    Add the components of matching or higher versions to the image.
  • When transitioning a VCF cluster from Baselines to vLCM Images using the VcfBaselineClusterTransition.ps1 script, the process fails during the compliance check phase with a DRAFT_CREATION_FAILED error. The generated resource-compatibility.json file displays INCOMPATIBLE components with error as below:

    Downgrades of manually added Components <name>(<version>) are not supported.

Environment

  • VMware Cloud Foundation 9.x

  • VMware vCenter 8.x

  • VMware vCenter 9.x

  • VMware ESXi 8.x

  • VMware ESX 9.x

Cause

  • This message appears when the ESXi host is currently installed with a newer VIB version than what the image provides. As such, vLCM is unable to downgrade the current newer version on the ESXi host.

  • The error is triggered because vSphere Lifecycle Manager (vLCM) is designed to move hosts toward a "Desired State." vLCM does not support automatic downgrades of "manually added" components (third-party drivers/VIBs) during a standard remediation if the version defined in the cluster image is older than what is currently running on the hardware.

  • In VCF environments, this typically happens when using the transition script's automated "Image Seeding" feature. The transition failure occurs because vLCM enforces strict downgrade protection. If the target vLCM image contains base ESXi versions but lacks specific standalone VIBs currently running on the ESXi hosts, the compliance engine will flag the configuration as INCOMPATIBLE to prevent a downgrade.

Resolution

Select and implement one of the following options, as appropriate for your specific environment configuration.

Option 1: Use this option if the VIB is no longer in use.

  1. SSH to the ESXi host.
  2. List/search for the VIB.

    esxcli software vib list |grep -i <vib name>

    Example

    esxcli software vib list |grep -i icen

  3. Check if the driver is in use.

    Network
    esxcli network nic list

    Storage
    esxcli storage core adapter list

    Reference: Determining Network/Storage firmware and driver version in ESXi.

  4. If the VIB is not in use, remove the VIB.

    esxcli software vib remove -n <vib name>

    Example

    esxcli software vib remove -n icen

    Reference: Instructions for uninstalling third-party VIBs from an ESXi host.

  5. Run the vLCM Image Compliance pre-check.

Option 2: Use this option if the VIB is still in use.

  1. If needed, download the corresponding driver VIB whose version is equal to or higher than what is currently installed on the ESXi host.

  2. Add the new VIB to the image, using components.

    1. Click on Cluster > Updates > Under Hosts > Image.
    2. Select Edit to edit the image.
    3. For components section, click Show details.
    4. Click Add Components.
    5. Under Show: Select appropriate component type ("All components", "Independent components", or "Independent components and Vendor Addon Components"), selecting All will show all available driver VIBs.
    6. Use filter option to search for the given driver name or type.
    7. Select the newer version to match the version shown in the downgrade error from the compliance check.
    8. Click "Select" to add the component to the image.
    9. Repeat Step 4 until all drivers/components have been added that are downgrades for the image.

     

  3. If the driver is not in the list of components, upload the new VIB to the Image Depot and follow step 2.

    Reference: Newer versions of a vendor addon might be missing when configuring a Lifecycle Manager cluster image in vCenter Server 7.0/8.0.
    Working with Images.

  4. Validate and Save the image for the cluster.

  5. vLCM should automatically trigger a compliance check on the hosts in the cluster.

For VCF environment using the VcfBaselineClusterTransition.ps1 script:

  1. Identify the incompatible Components from the Transition logs.
  2. Update the target vLCM image to explicitly include the missing VIBs identified. Ensure the component versions included in the image match or exceed the versions currently installed on the host.
    (Note for VCF: Since auto-seeded images in SDDC Manager cannot be edited directly, we must build the correct image on a temporary cluster in vCenter, then use the transition script menu to import it into SDDC Manager).
  3. Re-run the VcfBaselineClusterTransition.ps1 script using the updated image. 

Additional Information

Powered by Wolken Software