I have tried to logon to the vcentre this morning but I cannot get the service to start, all the other services are loading fine. Is this part of the bug or has something else happened to my vcentre???

Unless I can get the vcentre working I will be unable to run the auto-patch.

Lee Richardson

Hi guys!

i´ve tried to install this patch in my 5 esx servers, and i have a problem with two of them, in these i have not a esxupdate command, the esx version is the same (3.5.0.103908) in 5 servers and i can not run update manager in them because failed metadata, another command to update it??

Thanks.

Installed the critical fix trough VC Update mechanism and now everything works fine again. Thx to VMware for this fix.

I'll second this - we were patching (intendeing to go to U1) on the day U2 was released.

Initially before scan for updates we saw U2 mentioned - after the scan it had gone (at the time we thought this was perhaps that it had been pulled). However when we remediated none of the listed patches were called 'Upgrade 2' so we thought we were safe to continue and did so.

On checking version we found we had done Upgrade 2 as well. As it is our dev area we didn't panic but were a little annoyed at the lack of clarity in the tool. Obviously yesterday we became a little more cheesed off about it.

And to allk thjose saying M$ do worse - yes they have done but at least when I am installing a service pack to an OS it clearly lists itself as a service pack so I can understand the risk I am taking on!!

I hope one lesson learned from this is that VM make their patch labelling much clearer.

Sure the 'perfect & smug people' can heap scorn on those of us who were misled but it seems to have hit more than just the novices so perhaps worth addressing?

by using the esxupdate command you need to have get the host in maintenance mode:

eg:
root@talx01 ESX350-200806812-BG# esxupdate update
INFO: No repository URL specified, going with file:///var/updates/ESX350-200806812-BG
INFO: Configuring...
ERROR: This bundle requires the host to be in maintenance mode. Since the host is not in maintenance mode, esxupdate cannot proceed. The VMs need to be turned off or migrated to another host first.
root@talx01 ESX350-200806812-BG#

I am logged onto my esx server ui because my vcenter is down, but I cannot see any options to migrate my current vms???

If I changed the dates on my esx servers would my vcentre come back online???

Lee Richardson

Lee,

This issue doesnt affect the Virtual Center, so you must be experiencing some other problem too.

You cannot VMotion when you connect your Virtual Client directly to the ESX Box since you are only seeying part of your infrastructure, VMotion is a Virtual Center based/controlled feature.

I reported this problem in this thread http://communities.vmware.com/message/1019825#1019825