I began seeing this during upgrade testing last night in my lab but decided to wait a day to see if other people were having the same problems I was. It is now being reported in various threads in the vSphere Upgrade & Install forum that vSphere 4.1 Update 1 upgrade files are failing to import into VMware Update Manager (VUM). What I’m consistently seeing in multiple environements is:
- .zip files which upgrade ESX and ESX from 4.0 to 4.1u1 will import into VUM successfully.
- .zip files which upgrade ESX and ESX from 4.1 to 4.1u1 fail to import into VUM.
- I have not tested the upgrade files for ESX(i) 3.5 to 4.1u1.
The success and error message for all four .zip file imports are shown below. Two successful. Two failures.
MD5SUM comparisons with VMware’s download site all result in matches. I believe there is invalid metadata or corrupted .zip files being made available for download.
The workaround is to create a patch baseline in VUM which will instruct VUM to download the necessary upgrade files itself which is an alternative method to utilizing upgrade bundles and upgrade baselines in VUM.