ESXi upgrade failing with the error “Remediate entity: Cannot execute upgrade script on host”

Products

• VMware vSphere ESXi

Issue/Introduction

ESXi update fails with the following error during remediation:

Error in vCenter VUM logs(/var/log/vmware/vmware-updatemgr/vum-server.log):

 

yyyy-mm-ddTZ error vmware-vum-server[10493] [Originator@6876 sub=SingleHostUpgradeRemediateTask.SingleHostUpgradeRemediateTask{31}] [singleHostUpgradeRemediateTask 373] 
Error running check scripts on host: esxihost.fqdn host Id: host-XXXX, error: Fault cause: integrity.fault.HostUpgradeRunScriptFailure

Backtrace:

yyyy-mm-ddTZ error vmware-vum-server[10493] [Originator@6876 sub=SingleHostUpgradeRemediateTask.SingleHostUpgradeRemediateTask{31}] [singleHostUpgradeRemediateTask 373]
[backtrace begin] product: VMware Update Manager, version: 8.0.3, build: 24853646, tag: vmware-vum-server, cpu: x86_64, os: linux, buildType: release
--> backtrace[00] libvmacore.so[0x00531DD5]
--> backtrace[01] libvmacore.so[0x00421834]
--> backtrace[02] libvmacore.so[0x00434013]
--> backtrace[03] libvci-vcIntegrity.so[0x007F95B1]
--> backtrace[04] libvci-vcIntegrity.so[0x008C2F71]
--> backtrace[05] libvmacore.so[0x0037EC04]
--> backtrace[06] libvmacore.so[0x00384517]
--> backtrace[07] libvmacore.so[0x00510FC5]
--> backtrace[08] libpthread.so.0[0x00008EB0]
--> backtrace[09] libc.so.6[0x000FFADF]
--> backtrace[10] (no module)
[backtrace end]

Additional log snippet:

yyyy-mm-ddTZ info vmware-vum-server[10493] [Originator@6876 sub=MaintenanceModeGuard]
[singleHostUpgradeRemediateTask 424] Host was already in maintenance mode, or request to keep in maintenance mode, skipping exit

Error on VUA logs(/var/log/vmware/vmware-updatemgr/vum-server/hostUpgrade):

ERROR:root:Failed to perform image profile update: File path of '/bin/nvidia-vgpud' is claimed by multiple non-overlay VIBs for embeddedEsx: {'NVD_bootbank_NVD-VMware_ESXi_8.0.0_Driver_535.261.04-1OEM.800.1.0.20613240', 'NVD_bootbank_NVD-VMware_ESXi_7.0.2_Driver_535.183.04-1OEM.702.0.0.17630552'}

 

yyyy-mm-ddTZ info vua[65509075] [Originator@6876 sub=VUA] Command '/tmp/vuaScript-gP3SsO/prep.py --ip=ipaddress' finished with exit status 1 stderr: INFO:Metadata.py:Reading /tmp/vuaScript-gP3SsO/metadata.zip INFO:imageprofile:Adding VIB VMW_bootbank_iavmd_3.0.0.1010-13vmw.803.0.79.24859861 INFO:imageprofile:Adding VIB VMW_bootbank_rd1173-esxio_0.1-1vmw.803.0.0.24022510 INFO:imageprofile:Adding VIB VMW_bootbank_rshim_0.1-12vmw.803.0.35.24280767

 

 

Environment

• VMware ESXi 7.x

• VMware ESXi 8.x

 

Cause

This issue typically occurs when a vendor modifies details of an existing VIB (for example, VIB name, vendor name, or version).

During the upgrade, the existing VIB on the ESXi host and the new VIB being introduced both attempt to claim the same file path.
Since two VIBs cannot claim the same file (unless they are identical), the upgrade fails with an integrity.fault.HostUpgradeRunScriptFailure error.

Resolution

1. Engage the hardware vendor to confirm:

   • Whether there has been a change in VIB name or vendor details.

   • If the existing VIB can safely be removed.

2. Remove the conflicting VIB from the ESXi host:

esxcli software vib remove --vibname=<VIB_NAME> --dry-run (The output of this command will indicate whether the removal would be successful, if a reboot is required, and which VIBs would be removed, without making any changes to the ESXi host. This allows for verification before proceeding with the actual removal.)