Hello,
I used VUM to apply 5.0 U3 fixes in ESXi 5.0 U2 hosts, but the build number after update is 1311177 instead of 1311175 as showed on "Correlating vCenter Server and ESXi/ESX host build numbers to update levels (1014508)" (http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=101450...) and "VMware ESXi 5.0, Patch ESXi500-Update03: VMware ESXi 5.0 Complete Update 3 (2055559)" (http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=205555...), so build 1311177 is Security-only.
How to apply the bugfixes too, please.
Thanks in advance.
You can download update-from-esxi5.0-5.0_update03.zip from http://support.vmware.com/selfsupport/download/ and install it using esxcli software vib command. Also you can download this update and deploy using UM.
Hi,
this is quite an interesting issue that you stumbled over ...
In fact Update 3 for ESXi 5.0 is the first patch bundle that I have ever seen that shows a higher build number for security-fixes-only (1311177) than for the regular build (1311175). So far it has always been the other way round (see e.g. my VIB matrix at http://vibmatrix.v-front.de).
I guess Update Manager will just apply the VIBs that have the highest build numbers and thus you end up with the esx-base VIB that has only the security patches. Not what you and me would expect. Can you please open a Support Request with VMware regarding this issue?
I will try to reproduce that and do the same.
Thanks
Andreas
Hello,
Well done, I bookmarked your spreadsheet. Thanks.
The issue happened with
"ESXi-5.0.0-2012090x001[s]-standard
9/27/2012
822948 (security-only)
821926 (all)" too.
Regards.
Sorry, I cannot reproduce your issue. I updated an ESXi 5.0 U2 host with Update Manager using the "VMware ESXi 5.0 Complete Update 3" patch, and after the reboot the host came up with build 1311175, not 1311177.
Can you please explain in detail what patches you applied?
What version of vCenter and Update Manager are you using?
I believe the issue is that if you do not update the ESXi 5.0 server to Update 3 but instead install all the patches before then it'll show the server as being on build 1311177. The Nessus scanner thinks 1311177 is the minimum level a host needs to have the patch installed but when you install Update 3 it is installed but the build number shows as 1311175.