VMware Infrastructure 3 v3.5 Update 1 (VI3 v3.5 U1) was released on April 10, 2008. Over the following weekend, we received reports that there were issues with the upgrade to VMware VirtualCenter 2.5 Update 1 (VC 2.5 U1), a component of VI3 v3.5 U1. As of 11 AM Pacific on April 15, 2008, we have confirmed that those issues have been resolved.
What You Should Do
If you have not yet downloaded the bits, you may do so at your convenience and proceed with the upgrade and installation. We have confirmed that the correct bits are available for download from http://www.vmware.com/download/vi/.
If you have already downloaded the bits, please confirm that you have the correct MD5SUM value for the .zip file before proceeding with installation, as per the details below. If you do not have the correct MD5SUM value, please re-initiate a download, and install from the .zip file that has the correct MD5SUM value. Please remember to clear out your Internet browser's cache prior to re-initiating the download.
Alternately, please download and install or upgrade to VirtualCenter 2.5 Update 1 using the VirtualCenter CD (ISO) image. This ISO file does not suffer from the MD5SUM mismatch issue that the VirtualCenter Zip file has encountered.
If you have already installed or upgraded to VC 2.5 U1, please verify that the .zip file used has the correct MD5SUM value mentioned below. If you do not have the correct MD5SUM value or if you are unsure about the MD5SUM value of the .zip file that you installed or upgraded from, and are experiencing any issues, please call in to VMware Support and open a support request (SR). There are no known issues associated with the VirtualCenter version installed using the .zip file with the incorrect MD5SUM value, but it is highly recommended that the correct .zip file for VC 2.5 U1 be used when installing or upgrading to VC 2.5 U1.
VMware Infrastructure 3 v3.5 Update 1 (VI3 v3.5 U1) was released on April 10, 2008. Over the following weekend, we received reports that there were issues with the upgrade to VirtualCenter 2.5 Update 1 (VC 2.5 U1), a component of VI3 v3.5 U1. As of 11 AM Pacific on April 15, 2008, we have confirmed that those issues have been resolved.
There were two primary topics discussed among the forum posters: one related to build numbers; and another related to incorrect VC 2.5 U1 bits.
1. Build numbers
As documented in the release notes at http://www.vmware.com/support/vi3/doc/vi3_esx35u1_vc25u1_rel_notes.html, the correct build numbers are as follows:
VMware Infrastructure Management Installer | 10 APR 2008 | Build 84782
VirtualCenter 2.5 Update 1 | 10 APR 2008 | Build 84767
Note: The VMware Infrastructure Management installer (Build 84782) includes the following packages:
VMware VirtualCenter Server 2.5 Update 1 Build 84767
VMware Update Manager 1.0 Update 1 Build 63965
VMware Converter Enterprise Update 1 for VirtualCenter 2.5 Build 62387
In other words, there are separate build numbers for the VirtualCenter installer and for the VirtualCenter Server itself. This is by design, and should not be a cause for concern. Given the confusion caused by the inconsistency, however, we are looking into ways to simplify the installation experience and better communicate such inconsistencies in the future.
2. VirtualCenter 2.5 Update 1 bits
The MD5SUM value for the correct VirtualCenter 2.5 Update 1 (.zip) file is:
If you have a different MD5SUM value than the above, please initiate another download from http://www.vmware.com/download/vi/ and confirm that the .zip file MD5SUM value is correct.
As surmised by several folks on the forums, incorrect bits were uploaded to the content distribution network that we use to support volume downloads. The situation has been rectified and we have confirmed that the correct bits are now available. If for some reason, you are still seeing incorrect MD5SUM values, please let us know by posting on this thread.
We sincerely regret and apologize for the inconvenience caused as a result of this issue. We are taking necessary steps to identify and rectify issues in our release infrastructure processes and systems to ensure that this does not happen again in the future.
VMware Infrastructure Product Management
Message was edited by: jasonboche
Appended to the end of the title because the original upgrade thread was locked and now references this thread