Please Check your ESXi version by following command and build number and compare it with this link:
esxcli software version getPlease mark my comment as the Correct Answer if this solution resolved your problem
It shows 6.7 Update 2.
I have even tried reinstalling vCenter thinking it may be corruption.
it says that I need Update 2 and some other patches
I've seen similar thing in the past, where custom images either didn't contain all vibs, or were just missing some bulletins.
Please provide a detailed list of what exactly Update Manager reports as missing.
It reports it is missing ESXi670-Update02, ESXi670-201904225-UG, ESXi670-201905001, ESXi670-201906002, and ESXi670-201904001.
So what is interesting is that I am running the custom Dell image 6.7 Update 2 and that is what it shows when I log in with the CLI and look at the version. However, vCenter shows VMware ESXi, 6.7.0, 13981272 looks like the most current version. If it is running ESXi 6.7 EP 10, why would it say I need ESXi 6.7 U2?
ESXi 6.7 EP 10 ESXi670-201906002 06/20/2019 13981272 N/A ESXi 6.7 EP 09 ESXi670-201905001 05/14/2019 13644319 N/A ESXi 6.7 EP 08 ESXi670-201904001 04/30/2019 13473784 N/A ESXi 6.7 U2 ESXi 6.7 U2 04/11/2019 13006603 N/A
I Think it's better to check and compare installed VIB lists of specified ESXi (your Dell Customized) with another host in same version.
esxcli software vib list
Is there any difference? or missing VIB?Please mark my comment as the Correct Answer if this solution resolved your problem
From what I saw so far, these are no missing vibs, but just indicators regarding installed patches, which are not included in the custom image (I saw the same with HPE images). You may run an update and apply these indicators, or do it with the next update. From a technical point of view, this shouldn't change anything.
I do not have another host to compare to. What is the potential harm if I go ahead and try to install these?
Try to install your Source inside a Virtual Machine, is there same error if you add it to your datacenter?! (let VUM Check it first)
Goal of ESXi customization is only separation of related VIBs to each of physical server platform (HP, Dell, IBM, Cisco, ...) and causing more compatibility inside each of Hosts.Please mark my comment as the Correct Answer if this solution resolved your problem
I just found another post - looks like may be the same issue.
I called this into VMWare support and they went through the list of updates that were pending("missing") and compared them to my version. They said none of those updates are needed and that it was an issue with 6.7u2 reporting that should be fixed in u3. I am not sure how accurate all that is, but that is what they told me.
I looked at the VIBs in the recent patch release, and I do have these installed. So this looks like a vCenter issue.
esx-base 6.7.0-2.60.13981272 VMware VMwareCertified 2019-07-16
esx-dvfilter-generic-fastpath 6.7.0-0.0.8169922 VMware VMwareCertified 2019-05-18
esx-ui 1.33.3-13454473 VMware VMwareCertified 2019-05-24
esx-update 6.7.0-2.60.13981272 VMware VMwareCertified 2019-07-16
esx-xserver 6.7.0-0.0.8169922 VMware VMwareCertified 2019-05-18
lsu-hp-hpsa-plugin 2.0.0-16vmw.6220.127.116.1102608 VMware VMwareCertified 2019-05-18
lsu-intel-vmd-plugin 1.0.0-2vmw.618.104.22.16802608 VMware VMwareCertified 2019-05-18
lsu-lsi-drivers-plugin 1.0.0-1vmw.622.214.171.12406603 VMware VMwareCertified 2019-05-18
lsu-lsi-lsi-mr3-plugin 1.0.0-13vmw.6126.96.36.19902608 VMware VMwareCertified 2019-05-18
lsu-lsi-lsi-msgpt3-plugin 1.0.0-9vmw.6188.8.131.5206603 VMware VMwareCertified 2019-05-18
lsu-lsi-megaraid-sas-plugin 1.0.0-9vmw.6184.108.40.20669922 VMware VMwareCertified 2019-05-18
lsu-lsi-mpt2sas-plugin 2.0.0-7vmw.6220.127.116.1169922 VMware VMwareCertified 2019-05-18
lsu-smartpqi-plugin 1.0.0-3vmw.618.104.22.16802608 VMware VMwareCertified 2019-05-18
native-misc-drivers 6.7.0-2.48.13006603 VMware VMwareCertified 2019-05-18
rste 2.0.2.0088-7vmw.622.214.171.12469922 VMware VMwareCertified 2019-05-18
vmware-esx-esxcli-nvme-plugin 126.96.36.199-2.48.13006603 VMware VMwareCertified 2019-05-18
vsan 6.7.0-2.60.13805960 VMware VMwareCertified 2019-07-16
vsanhealth 6.7.0-2.60.13805961 VMware VMwareCertified 2019-07-16
tools-light 10.3.5.10430147-12986307 VMware VMwareCertified 2019-05-18
So it means if you setup vCenter 6.7 U1 or any older versions there is no problem?!
But if you have only one host, stop VUM service inside VCSA management or remove its scheduled checking interval. So I think there will be no more warning from Update Manager.Please mark my comment as the Correct Answer if this solution resolved your problem
The response from VMware support basically confirms that it is more of a cosmetic issue, so don't worry about it.