vCenter Update 2 Agent Issues

[esnmb]

I am trying to upgrade vCenter U1 to U2 and ran the agent upgrade checker, which returned some failures.  I have a few 4.1 hosts in my environment still, and they spit out the "The ESXi host doesn't have enough available memory to install vCenter  agent(s)." message.

Can this be ignored, or do I need to install that patch referenced in the article http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=101626...

Thanks.

[esnmb]

BTW, that is vCenter 5.0 I am running now...

[zXi_Gamer]

upgrade vCenter U1 to U2

Can you confirm on the version 4.1 or 5.0? since this kb looks more a match for you if you are using 5.0.

[esnmb]

I just saw that article!  I am running 4.1 and have just now put a host into maintenance mode and rebooted it. I'll run the checker once it's up and let you know.

[esnmb]

Do we know what happens if I upgrade vcenter anyway?  Will the hosts be disconnected?

[esnmb]

So that reboot cleared up the failure for that host.  On to the next!

I do have two hosts that can't be rebooted as I have to pin VM's to them..  That is why I am wondering what happens if I proceed with the upgrade regardless of the failures.

[zXi_Gamer]

I do have two hosts that can't be rebooted as I have to pin VM's to   them..  That is why I am wondering what happens if I proceed with the   upgrade regardless of the failures.

Well, your vsphere will be upgraded to the latest version. However it will not be able to manage the ESX hosts, since the vpxa agents[vsphere] agents cannot be pushed to the ESX servers.

Regarding your VMs, they will be still operational since they are running in the ESXi hosts without downtime, provided you have not configured DVS or set cluster configurations.

[esnmb]

How about I remove them from vCenter prior to the upgrade, then add them back in?

[zXi_Gamer]

Well, that is a possible workaround as mentioned in the kb. When you are removing the esx hosts from the vc, the existing vpxa agents get uninstalled, so freeing up the space.

When the esx is added to the new vc, the new vpxa gets pushed. Now the real catch is the size of the vpxa which gets pushed to the servers/

[esnmb]

Interesting.  Perhaps I will try one of them.