ESXi Staging Fails with VibValidationError for circuit_rewind_bootbank_ipmitool in vSphere Lifecycle Manager

Products

• VMware vCenter Server 8.0

Issue/Introduction

When attempting to stage or remediate an ESXi host patch lifecycle task via vSphere Lifecycle Manager (vLCM) or vSphere Update Manager (VUM), the operation fails during the staging phase.

Task events in the vSphere Client present a metadata validation error : Staging did not succeed for the ESXi Host.

Review of the vmware-vum-server.log and esxupdate.log on the vCenter Server and  ESXi Host  displays the following signature:

/var/log/vmware/vmware-updatemgr/vum-server/vmware-vum-server.log

YYYY-DD-MMTHH:MM:SS info vmware-vum-server[1482986] [Originator@6876 sub=HostUpdateDepotManager] [installer20 83] Processing the Stage results for host: ####(Ent--> <esxupdate-response>
--> <version>1.50</version>
--> <error errorClass="VibValidationError">
--> <errorCode>8</errorCode>
--> <errorDesc>An error occurred validating VIB contents.</errorDesc>
--> <problemset>
-->   <problem>VIB circuit_rewind_bootbank_ipmitool_1.8.18 violates extensibility rule checks: ['(line 24: col 0) Element vib failed to validate content']</problem>
--> </problemset>
--> </error>
--> </esxupdate-response>

/var/log/esxupdate.log

YYYY-MM-DDTHH:MM:SS Er(11) esxupdate [3524928]: esximage.Errors.VibValidationError: VIB circuit_rewind_bootbank_ipmitool_1.8.18 violates extensibility rule checks: ['(line 24: col 0) Element vib failed to validate content']

Environment

VMware vSphere ESXi 8.x

Cause

The update engine blocked the staging process due to a third-party VIB (circuit_rewind_bootbank_ipmitool_1.8.18)  residing on the host that fails modern vSphere Lifecycle Manager (vLCM) metadata compliance checks

Resolution

[Note: Before proceeding with below steps, ensure that the vib is not currently in use]

To resolve this issue, you must manually remove the non-compliant, legacy CommunitySupported VIB from the host CLI.

1. Place the affected ESXi host into Maintenance Mode via the vSphere Client.

2. Establish an SSH session to the ESXi host using root credentials.

3. Verify the exact name of the VIB present on the system by executing:

   esxcli software vib list | grep ipmitool
   

4. Remove the non-compliant package by running the following command:

   esxcli software vib remove -n circuit_rewind_bootbank_ipmitool
   

5. If the command output states Reboot Required: true, reboot the host using the CLI or vSphere Client:

   reboot
   

6. Once the host reconnects, reinitiate the staging or remediation task within the vSphere Client lifecycle dashboard.

Additional Information

For more information regarding host image profiles and enforcement thresholds, see techdocs reference :  Manage the Acceptance Levels of ESXi Hosts and vSphere Installation Bundles