vmwaredownload
Enthusiast
Enthusiast

cannot upgrade ESX4 to ESX 4 Update1

Hi,

After upgrading Vcenter 4 to vCenter 4 Update1 and putting the ESX 4 Update 1 iso into the Update Manager repository

i created a baseline..when trying to remdiate my ESX 4 hosts, im gettin the following error:

Upgrade is not supported from host version 4.0.0 build 175625 to release version 4.0.0 update 1

Build 208167

and

0 Kudos
48 Replies
davisjj
Contributor
Contributor

I am having the same problem. I followed these steps in attempting the upgrade:

1. Upgrade vCenter (VIM) server (all components) with VMware-VIMSetup-all-4.0.0-208156.iso

2. Create host upgrade baseline with VMware-VIMSetup-all-4.0.0-208156.iso (did not upload ESXi .zip file, not using ESXi)

3. Attached baseline to ESX hosts running v4.0.0-175625

4. Scanned and attempted to remediate, received error: Upgrade is not supported from host version 4.0.0 Build 175625 to release version 4.0.0 Update 1 Build 208167.

Also, can someone tell me where the upgrade files are stored/uploaded to when you create a baseline? If I wanted to delete the baseline AND the uploaded content/files (to try again), how would I do that?

0 Kudos
davver
Enthusiast
Enthusiast

Hi,

I have the same problem. Upgraded Vcenter to U1 and when i try to upgrade the host, i have the same message.

The host is incompatible with the update.

Any ideas on this issue?

thx.

Davy

Regards, Davy
0 Kudos
chilow
Enthusiast
Enthusiast

You need to use the offline-bundle to upgrade an ESX 4.0 host to 4.0U1. Can your VUM server access the internet? If so, setup ESX 4.x patches to be automatically downloaded to the VUM server and create a new baseline.

Source URL for ESX 4.x patches: https://hostupdate.vmware.com/software/VUM/PRODUCTION/index.xml

0 Kudos
chilow
Enthusiast
Enthusiast

You need to use the offline-bundle to upgrade an ESX 4.0 host to 4.0U1. Can your VUM server access the internet? If so, setup ESX 4.x patches to be automatically downloaded to the VUM server and create a new baseline.

Source URL for ESX 4.x patches: https://hostupdate.vmware.com/software/VUM/PRODUCTION/index.xml

0 Kudos
davver
Enthusiast
Enthusiast

Hi,

My VUM Server can reach the internet. The VUM downloaded the U1 rollup.

I made a new baseline to upgrade the host. After i attached the baseline, i scan the host and get the message 'host incompatible'.

I noticed the download package on the vmware site. I will try the upgrade tomorrow with the package.

But it should work with the VUM also?! Or am i wrong?

Regards,

Davy

Regards, Davy
0 Kudos
davisjj
Contributor
Contributor

Thanks. I have that URL setup (was included with the default configuration I guess).

I am being told by VMWare support that I will need to do the following (manual host-by-host upgrade, so it would seem):

*********************************

In order to upgrade host download patch to /tmp

Then run following commands

#cd /tmp

#esxupdate --bundle=ESX-4.0.0-update01.zip update

*********************************

I am getting ready to try this.

0 Kudos
chilow
Enthusiast
Enthusiast

It should work with VUM, it worked in my test lab.

I...

-Updated vCenter4 to update1

-Updated VUM to update1

-downloaded new VUM client and installed

-created a ESX4.0 u1 baseline (fixed) using 'ESX4.0 complete update 1'

-attached baseline to test cluster

-scanned the two hosts for Patches and extensions

-upgraded hosts

0 Kudos
davisjj
Contributor
Contributor

That's the same path that I followed. Could it have anything to do with customized partitions on the ESX hosts (mainly some larger than the default size)? I thought I read somewhere that those could cause an issue during the update process.

In any event, the semi-manual update process that support directed me to is working so far (one out of four hosts completed).

*********************************

In order to upgrade host download patch to /tmp

Then run following commands

#cd /tmp

#esxupdate --bundle=ESX-4.0.0-update01.zip update

0 Kudos
chilow
Enthusiast
Enthusiast

I also modified the partition sizes during the install of ESX 4.0. Are you using the Cisco Nexus 1000v module?

0 Kudos
davisjj
Contributor
Contributor

No, we are not using the Nexus (our implementation is still relatively small), but one of our other sites is going to.

Ok, I finished up all four hosts and they are happily running Update 1. Not the ideal process and I would still like to have an explanation from VMWare as to why we had to do it this way, but at least we are current again.

0 Kudos
joshp
Enthusiast
Enthusiast

If you have automatic downloads enabled for VUM you should have an entry in the available patches called "VMware ESX 4.0 Complete Update 1". All you need is to add the patch to an existing "fixed" baseline or use the default "dynamic" baseline called "Non-Critical Host Patches". You do not need to create a "Upgrade Baseline", use a "Patch Baseline". After the patch is applied ESX will be running build 208167.

VCP 3, 4 www.vstable.com
0 Kudos
davisjj
Contributor
Contributor

More on this from support:

Using one of two approaches esxupdate command is simple. Reason for VUM gives error message

The conflict is due to a dependency in ESX 4.0 Update 1. When applying this rollup it checks for the latest VEM module. The workaround is to create two baselines, one with Update 1 and the other with the Cisco update.

First remediate the VEM update and then in a second motion apply Update 1.

If these two updates are included in the same remediation process Update 1 seems to be the first attempt and will fail. Update Manager will continue after the Update 1 failure and install the VEM update however result will be an overall failure as some packages could not be installed. A second run of the same baselines will then have to be run to install Update 1.

0 Kudos
ITCORESYS
Enthusiast
Enthusiast

You need to use the offline-bundle to upgrade an ESX 4.0 host to 4.0U1. Can your VUM server access the internet? If so, setup ESX 4.x patches to be automatically downloaded to the VUM server and create a new baseline.

Source URL for ESX 4.x patches: https://hostupdate.vmware.com/software/VUM/PRODUCTION/index.xml

VUM is setup on mine to use that exact patch source, but the "offline-bundle" you speak of is not getting downloaded into my VUM repository and therefore is not visible to add to a baseline.

Only the ESXi one is downloading.

0 Kudos
ITCORESYS
Enthusiast
Enthusiast

If you have automatic downloads enabled for VUM you should have an entry in the available patches called "VMware ESX 4.0 Complete Update 1". All you need is to add the patch to an existing "fixed" baseline or use the default "dynamic" baseline called "Non-Critical Host Patches". You do not need to create a "Upgrade Baseline", use a "Patch Baseline". After the patch is applied ESX will be running build 208167.

I dont have the entry.

I do have the "VMware ESXi 4.0 Complete Update 1" entry, not the ESX one though.

0 Kudos
ITCORESYS
Enthusiast
Enthusiast

Heres a combined answer for you:

This entire process is buggy, tribal and terribly documented.

VUM 4 U1, does not download "ESX 4 Complete Update 1" patch for me, and apparently doesnt download for you either. (Only the ESXi one shows in my repository, even after a full complete uininstall and reinstall of EVERYTHING)

Creating an upgrade baseline and uploading either the .zip or the .iso does NOT work for ESX4.

The .ISO uploads fine, but the remediate bombs with an unknown error (Unsupported host error in the esxupdate log file on the host itself).

The .zip fails with a checksum error even though the checksum matches whats posted on their download page.

The only thing that worked for me was to run it manually from the service console command line by:

1) copy ESX-4.0.0-update01.zip file to the host's local drive using a shared drive like iSCSI or NFS or using SCP/Veeam.

2) run "esxupdate --bundle=ESX-4.0.0-update01.zip update" from the command prompt on the host.

3) Reboot

0 Kudos
nanders
Contributor
Contributor

Hi,

We have the same problems...

  • VUM won't download the ESX 4 U1 (only for ESXi).

  • After building a baseline (from the ESX 4 U1 ISO file), VUM reports "incomapible".

We will try to manually update the host to night. It would be nice to hear from VMware why this isn't working as planned...

Thanks for your updates on this thread.

0 Kudos
mkopenski
Contributor
Contributor

We are having the same issue, hopefully someone will come back with an answer.

0 Kudos
ikroumov
Contributor
Contributor

Let me share my experience after the upgrade process I did last night.

We are running two HP ProLiant DL 580 G5 hosts. Both hosts at the begining of the upgrade were running vSphere 4.0 build 169780. The update which was released by VM Ware for November contains 37 updates. Few updates do not require reboot , one of the updates is U1 which has the the known issue. If you have downloaded the whole bundle via VM Ware Update manager, that is OK, do not panic !!!.

ESPECIALLY IF YOU ARE RUNNING HP SERVERS, DO THIS FIRST:

"" Upgrading ESX 4.0 to 4.0 U1 on HP Proliant system can fail or time out and leave the host in an unusable state if Insight Management Agents are already installed and running on the host being upgraded. VMware and HP are investigating interactions between VMware esxupdate tool and HP Insight Management Agents for a possible solution. ""

1. Disable this services:

• service hpsmhd stop

• service hp-snmp-agents stop

• service hp-health stop

2. During the initiate stage of the process, when you prepare the updates via VM Ware Update Manager (VUM). SET THE SERVER IN MAINTENANCE MODE BEFORE YOU PROCEED. BEGIN WITH THE UPDATE PROCEDURE. UNCHECK ALL THE UPDATES EXCEPT THOSE THAT DO NOT REQUIRE HOST REBOOT. If you want to know what is going on, you could monitor host performance via vCenter server and I do recomend running the linux "top" command checking live processes running on the host. The process wyou would be most interesting is ESXUPDATE.

3. Even that those updates do not require reboot, PLEASE REBOOT your host.

4. After the host come back online, its status will be DISCONNECTED on vCenter console. Try to connect to the host providing your root account and password. CONNECTING WILL FAIL the message will tell you that the host is not accessible or disconnected. THAT IS OK !!!! this is a good indication that your work is OK.

5. Reboot the host again. Wait intil the host come back, at this time when you try to connect to the server using the vCenter console, you will be able to connect to the server.

6. Do the remediation again against the same host which is still in maintenance mode. During the preparation stage, UNCHECK VMWARE ROLL UP U1 update. Select all the other updates that require host reboot.

7. Disable all the HP monitoring services specified in step "1". run the remediation process. Open esx linux console and run the same "top" command to monitor live all the processes. Again, the process "esxupdate" is what our attention will be focused on. After a little while the process will finish its job. Now, at this moment you have to take action. vCenter console will be showing progress 33% State-Processing. and it will fail giving you a message. time out. THIS IS OK, NO PANIC !!!! Go to the linux console and stop the life monitoring.

8. Reboot the host.

9. During the time when your server is coming up, at some point when it is starting / configuring "advanced-*****" ,sorry do not remember the whole name, but it begins with the word advanced, the server will hangs up doing nothing. Your vCenter console will be showing you Progress 33% and it will throw an error telling you that the process failed with an unexpected error. Restart the server manually and let it come again. At this time the server will come up.

10. Connect to the server via the vCenter console. At this moment you have two scenarios. Both of them ARE OK !!!

10.1 If your console does not connect to the server, reboot the host again. You will be in the same position as step "5".

10.2 If your console connects straight to the server you might have tho results

It doesn't matter if you come to this moment via step 10.1 or 10.2, your next step will be to check and ensure that the updates have been installed. Most likely the console will report that the updates have not been installed. This is not a lie !!!!! The console shows you what the is the current status of the update database is. If the file has been updated, you will see that the updates are OK, otherwise you will see the red circle " INCOMPATIBLE HOST"

11. Reboot the host again and wait until it comes up. Check it again to see whether the update file has been updated or not.

12. In case you see the same red cicrle, initiate remediation process again. Despite all the updates have been installed, you have to run the remediation process again because the host needs to go through the process so it will update the file tracking the update records.

13. At this moment your server will be OK and if you check its status, you will see its current build as vSphere 4.0 build 208167

14. YOU HAVE TO UPDATE THE VM TOOLS RUNNING ON ALL THE VIRTUAL MACHINES.

15. CHEERS !!!! Enjoy !!!

THE WHOLE PROCESS will take you up to three hours, depends how long your servers take to reboot.

Sincerely

I Krumov

0 Kudos
nanders
Contributor
Contributor

We have now successfully updated one of our host to ESX 4 Update 1. We followed ITCORESYS post. We are running on DELL r710 servers. Before we did the the manually update to U1 we applied all patches up to build 175625 thru Update Manager.

0 Kudos