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

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

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.

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

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.

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.

joshp wrote:

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.