OPERATIONAL DEFECT DATABASE
...
...
You stage and remediate an ESXi 7.0 against the "Non-critical Host Patches (Predefined)" baseline using vSphere Lifecycle Manager. This operation is finished successfully.Afterwards the ESXi is still showing as non-compliant, and stays this way even when you check compliance again. In vmware-vum-server-log4cpp.log, located in /var/log/vmware/vmware-updatemgr/vum-server/ you find the following entries: [2021-08-24 07:07:21:438 'HostUpdateDepotManager' 140230213986048 INFO] [scanHost20, 1317] Bulletin: intel-nvme-vmd-en_2.0.0.1146-1OEM.700.1.0.15843807 Release Type: extension Status: Installed ( [installed] conditions observed in vib : INT_bootbank_intel-nvme-vmd_2.0.0.1146-1OEM.700.1.0.15843807 ) [2021-08-24 07:07:21:438 'HostUpdateDepotManager' 140230213986048 INFO] [scanHost20, 1286] Bulletin: intel-nvme-vmd-en_2.5.0.1066-1OEM.700.1.0.15843807 Release Type: extension Status: Missing ( [Missing][Obsoletes Host] conditions observed in vib : INT_bootbank_intel-nvme-vmd_2.5.0.1066-1OEM.700.1.0.15843807 ) [2021-08-24 07:07:21:438 'HostUpdateDepotManager' 140230213986048 INFO] [scanHost20, 1286] Bulletin: intel-nvme-vmd-en_2.6.0.1345-1OEM.700.1.0.15843807 Release Type: extension Status: Missing ( [Missing][Obsoletes Host] conditions observed in vib : INT_bootbank_intel-nvme-vmd_2.6.0.1345-1OEM.700.1.0.15843807 ) [2021-08-24 07:07:21:438 'HostUpdateDepotManager' 140230213986048 INFO] [scanHost20, 1286] Bulletin: intel-nvme-vmd-en_2.6.1.1001-1OEM.700.1.0.15843807 Release Type: extension Status: Missing ( [Missing][Obsoletes Host] conditions observed in vib : INT_bootbank_intel-nvme-vmd_2.6.1.1001-1OEM.700.1.0.15843807 )
This issue is caused by the way the related VIBs were created. According to their metadata the older generation "intel-nvme-vmd" VIBs are supposed to replace the newer "iavmd" VIB, which according to its metadata is supposed to replace the ""intel-nvme-vmd" VIBs".vSphere Life Cycle Manager cannot resolve this circular reference and decide which of the packages is the latest one, and therefore ends up installing none of the VIBs.
This issue is resolved in ESXi 7.0 Update 3c.
To work around this issue, you can use a custom baseline instead of the predefined one, where you exclude the intel-nvme-vmd VIBs: In vSphere Client, go in Menu > Lifecycle ManagerSelect "Baselines"Select "Non-Critical Host Patches (Predefined)" and click on DUPLICATEEnter a name for the baseline and confirm with DUPLICATESelect the new baseline and click on EDITUnder "Matched" deselect the following Patches: intel-nvme-vmd-en_2.0.0.1146-1OEM.700.1.0.15843807intel-nvme-vmd-en_2.6.0.1345-1OEM.700.1.0.15843807intel-nvme-vmd-en_2.5.0.1066-1OEM.700.1.0.15843807intel-nvme-vmd-en_2.6.1.1001-1OEM.700.1.0.15843807 Continue and finish the wizardDetach the predefined baseline use your new custom baseline instead
Click on a version to see all relevant bugs
VMware Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
