VMware Cloud Community
pens
Contributor
Contributor

vSphere 4 build number mismatch

I was trying to determine if I had a specific patch installed (ESX400-200912401-BG), so I first check the vCenter Update Manager. It said my vSphere server was build number 244038 and that the patch was installed. When I log into the vSphere server directly I get this:

-bash-3.2# esxupdate query

-


Bulletin ID---- -


Installed--- -


Summary--


ESX400-200912402-SG 2010-04-09T14:47:29 Updates OpenSSL

ESX400-200912403-SG 2010-04-09T14:47:29 Updates NSS and NSPR

ESX400-200912404-SG 2010-04-09T14:47:29 Updates DHCP

ESX400-201002402-BG 2010-04-09T14:47:29 Updates initscripts

ESX400-201002404-SG 2010-04-09T14:47:29 Updates glib2

ESX400-201002406-SG 2010-04-09T14:47:29 Updates newt

ESX400-201002407-SG 2010-04-09T14:47:29 Updates nfs-utils

ESX400-201002408-BG 2010-04-09T14:47:29 Updates Enic driver

ESX400-201003401-BG 2010-04-09T14:47:29 Updates vmkernel64,vmx,hostd and scripts

ESX400-201003402-BG 2010-04-09T14:47:29 Updates hpsa driver

ESX400-201003403-SG 2010-04-09T14:47:29 Updates acpid

ESX400-201003404-BG 2010-04-09T14:47:29 Updates lpfc820 driver

ESX400-201003405-SG 2010-04-09T14:47:29 Updates samba-client and samba-common

ESX400-201003406-BG 2010-04-09T14:47:29 Updates megaraid-sas driver

ESX400-201003407-BG 2010-04-09T14:47:29 Updates ehci-ehci-hcd driver

ESX400-Update01a 2010-04-09T14:47:29 VMware ESX 4.0 Complete Update 1

-bash-3.2# vmware -v

VMware ESX 4.0.0 build-208167

The build numbers are complete different and the vSphere server doesn't think that the newer patches have been installed. I've tried rebooting and removing/re-adding the server to vCenter but the issue is still there.

Reply
0 Kudos
1 Reply
a_p_
Leadership
Leadership

Reply
0 Kudos