ESXi Upgrade Dry-Run Fails with DependencyError: QLogic VIBs (qedf, qedi) Conflict with ImageProfile

Products

• VMware NSX

Issue/Introduction

• During an upgrade or patching operation within VMware Cloud Foundation (VCF), vSphere Foundation (VVF), or a standalone ESXi environment, the upgrade pre-check or dry-run fails.

• The host upgrade log (e.g., esxupdate.log or vCenter LCM logs) reports an error explicitly citing a DependencyError regarding QLogic VIBs.

• Example log trace: [DependencyError] On platform embeddedEsx, VIB QLC_bootbank_qedf_2.74.1.0-1OEM.800.1.0.20613240 requires qedentv_ver = X.70.50.0, but the requirement cannot be satisfied within the ImageProfile. However, additional VIB(s) QLC_bootbank_qedentv_3.71.73.0-1OEM.800.1.0.20613240 from depot can satisfy this requirement.

Environment

VMware NSX

Cause

OEM or vendor-specific QLogic drivers (qedf and qedi) residing on the ESXi host contain strict version dependencies (qedentv_ver) that conflict with the base ESXi upgrade or patch bundle ImageProfile. The target ImageProfile cannot satisfy the required version of the interdependent OEM VIBs natively.

Resolution

To resolve this issue, the conflicting VIBs must be evaluated for active use and removed if not in use.

1. Verify Adapter Usage: Establish an SSH session to the affected ESXi host using root credentials. Execute the following diagnostic commands to verify if the storage or network topology actively utilizes the QLogic drivers:

   esxcli storage core adapter list
   esxcli network nic list
   

2. Remove Conflicting VIBs (Unused Hardware Scenario): If the qedf or qedi adapters are not actively bound to functional hardware, remove the conflicting VIBs from the host footprint. The --force flag ensures multiple -n arguments bypass local cross-dependency checks during the removal transaction:

   esxcli software vib remove -n qedf -n qedi --force
   

3. Commit State Changes: Reboot the ESXi host to commit the VIB removal and initialize the updated bootbank.

4. Re-initiate Upgrade: Once the host reconnects to the management plane, re-initiate the upgrade dry-run or pre-check workflow.

Note on Active Hardware Validation: If the host actively utilizes these adapters for storage or network I/O, the drivers cannot be removed. In such instances, the administrator must stage the complete, compatible OEM driver bundle (containing matching versions of qedentv, qedf, qedi) and apply the VIBs simultaneously to satisfy all cross-dependencies prior to attempting the ESXi base upgrade.