PlatinumHMC
Contributor
Contributor

HPE 6.7 U3 Custom ISO - VUM says 6.7 U2/U3 not installed

Fresh install on an HPE DL380 gen10 using HPE 6.7 U3 Custom ISO with VCSA 6.7 U3a.

In the Critical Host Patches predefined baseline, VCSA shows three missing items:

  • Updates elx-esx-libelxima.so VIB
  • VMware ESXi 6.7 Complete Update 2
  • VMware ESXi 6.7 Complete Update 3

The Non-Critical Host Patches predefined baseline also shows a number of patches missing which are included in 6.7 U2 and U3.  When viewing the Updates tab for the host, the "Installed on Host" section shows 6.7.0 build 14320388 which corresponds with 6.7 U3.

Is there some way to correct VUM so it properly see the host is running 6.7 U3 and stops reporting that it needs patches which are already installed?

0 Kudos
4 Replies
blazilla
Enthusiast
Enthusiast

Hi,

can you provide a screenshot? What  build level has the ESXi host?

Best regards Patrick https://www.vcloudnine.de
0 Kudos
Alex_Romeo
Leadership
Leadership

Hi,

This doesn't solve your problem, but they faced a similar problem to yours. You can take inspiration:

After installing a HP ESXi 6.7u2 image from VMWare, Update Manager still shows 6.7 complete update 1...

ARomeo

Blog: https://www.aleadmin.it/
0 Kudos
PlatinumHMC
Contributor
Contributor

Screenshots below.

2019-11-30 13_47_56-vSphere - prdp-h01-ilrm.ephmc.com - Updates.png

2019-11-30 13_48_15-vSphere - prdp-h01-ilrm.ephmc.com - Updates.png

0 Kudos
Psychomike70
Contributor
Contributor

Same issue. I just finished installing the HPE Custom ISO for 6.7 U3 December build 151xxxx. When VUM ran the compliance scan it is telling me it is missing the same patches you have listed...but the host shows the correct build number (latest version). I plan on going through all the installed VIBs, but I am not excited about running patches against a host that is already supposed to be on the latest build/custom ISO. Seeing how I rebuilt these due to having hosts go "not responding" to the point I can't get to the DCUI (but the VMs still running), I don't want to introduce any potential issues...but they are listed as Critical Bug fixes (that are supposed to be cumulative so why even read it needs U2 and U3)....and on top of my "Out of Memory" Active Directory authentication reverting back to local issues that still have an open ticket....

0 Kudos