Thursday, August 5, 2010

ESXi 4.0 – 4.1 Planning

Writing this thanks to gogo wireless… Love this service.

I'm going to start upgrading our hosts to 4.1 next weekend probably. Going to try update manager even though it crashed and burned on my 3.5-4.0 upgrade and I ended up using the host utility. I know the command line upgrader works.

I read this on the spiceworks message board:

Resolution:

This is worth knowing as it's a bug and definate gotcha.

VMWare said:

"I had one of the escalation engineers for Update Manager look at the log and here is what he said

The customer imported the pre-upgrade offline bundle which is NOT needed and in fact causes problems.

[2010-07-28 13:36:55:781 'DownloadOfflinePatchTask.DownloadOfflinePatchTask{9}' 3700 INFO] [vciTaskBase, 530] Task started...

[2010-07-28 13:36:55:781 'DownloadOfflinePatchTask.DownloadOfflinePatchTask{9}' 3700 INFO] [downloadOfflinePatchTask, 123] Upload offline bundle: C:\Windows\TEMP\vum8205261630712700578.pre-upgrade-from-ESX4.0-to-4.1.0-0.0.260247-release.zip

We are working on correcting the situation so this doesn't happen. The existing pre-upgrade bundle will be replaced and we are working on a KB for those that have gotten into the situation (iKB 1024805). Unfortunately, there is no easy workaround once VUM is in this situation. A reinstall/DB reinit is suggested."

The end result is that VUM didn't want to reinstall cleanly so I had to nuke my Vcenter server and rebuild it from scratch.

So, DON'T APPLY THE PRE-UPGRADE PACKAGE IF YOU ARE USING UPDATE MANAGER TO UPGRADE YOUR ESX HOSTS!

:)


 

Maybe useful next weekend J

No comments: