fujitsu-upgrade & hti-upgrade VIBs marks baseline as Incompatible on Non-Fujitsu/Hitachi Servers

Products

• VMware vCenter Server
• VMware vCenter Server 8.0

Issue/Introduction

Custom Upgrade baseline showing as "Incompatible" in vCenter lifecycle manager (vLCM) when trying to remediate it.

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

YYYY-MM-DD HH:MM:SS info vmware-vum-server[60055] [Originator@6876 sub=HostUpgradeScanner] [scannerImpl 663] Precheck script test result: 'SUCCESS', test 'ENTROPY_CACHE', expected 'True', found 'True' and errortype is 45
YYYY-MM-DD HH:MM:SS info vmware-vum-server[60055] [Originator@6876 sub=HostUpgradeScanner] [scannerImpl 1065] Host needs upgrade.
YYYY-MM-DD HH:MM:SS info vmware-vum-server[60055] [Originator@6876 sub=HostUpgradeScanner] [scannerImpl 1768] (vmodl.LocalizableMessage) [
-->    (vmodl.LocalizableMessage) {
-->       key = "com.vmware.vcIntegrity.HostUpgrade.MissingDependencyVibs",
-->       arg = (vmodl.KeyAnyValue) [
-->          (vmodl.KeyAnyValue) {
-->             key = "precheckError",
-->             value = "FJT_bootbank_fujitsu-upgrade_7.0.3-532.1.1
--> HTI_bootbank_hti-upgrade-vib_1.4.0-6OEM.703.0.0.20842708
--> "
-->          }
-->       ],
-->       message = <unset>
-->    }
--> ]

 

YYYY-MM-DD HH:MM:SS error vmware-vum-server[2247075] [Originator@6876 sub=VciClusterRemediateCheckTask.VciClusterRemediateCheckTask{759}] [vciClusterRemediateCheckTask 166] Found incompatible software config on host: <Hostname>, host Id: <host-ID>, error: Fault cause: integrity.fault.HostUpgradeIncompatibleSoftwareConfig
-->
YYYY-MM-DD HH:MM:SS error vmware-vum-server[2247075] [Originator@6876 sub=VciClusterRemediateCheckTask.VciClusterRemediateCheckTask{759}] [vciTaskBase 714] Task execution has failed: Fault cause: integrity.fault.HostUpgradeIncompatibleSoftwareConfig
-->

Note: In the example shared above, the ESXi was running on a Cisco hardware, however, the VIBs were for Fujitsu and Hitachi hardware. The upgrade baseline was created using Cisco custom ISO.

Cause

If any unwanted VIB will be present/installed in the ESXi host that is for a different hardware vendor than the vendor of the custom image used to create the baseline, the baseline will me marked as "Incompatible".

Output of "esxcli software vib list" command will confirm the VIBs highlighted in the screenshot/log snippets referred above.

Resolution

Remove the VIBs that are creating the conflict using the following command and reboot the ESXi host if the output show "Reboot Required: true":

• esxcli software vib list -n <VIB-Name>