Alternative Patch Process and Updates on the VMware AUG 12 time bomb BUG
August 15th, 2008 | 
Author: Being that it is the end of the week and I have fallen a day or so behind in keeping up with the VMware updates for the August 12 time bomb bug, I decided that I would post the remaining emails I received from VMware. I’m also including an update from John Troyer from the VMTN Blog providing some clarity on version number information differences between the install media and the express patched ESX/ESXi 3.5 versions.
On Thursday 8.14 there were three separate notifications from VMware. 2 of the 3 emails were specifically about the replacement of the install media for ESX/ESXi 3.5 Update 2. The last email offers an alternative patch process for applying the express patches to impacted environments already running ESX/ESXi 3.5 Update 2.
Install Media
The install media, downloadable from the VMware web site, is only relevant (in the context of this bug) to customers that had not already upgraded to Update 2. VMware had pulled the media with the period expiration enabled from their site earlier this week, and was working to provide the bug free replacement media by 6 PM PST on Wednesday August 13.
After realizing they could not meet that deadline, VMware sent the FOURTH UPDATE email which I received at 1:04 AM EST on August 14:
Dear VMware Customer,
This message is to inform you that we are experiencing a delay in releasing the new version of ESX/ESXi 3.5 Update 2. Our testing of this release is taking longer than anticipated. We are now targeting to release the update between 2:00 AM PDT (0700 UTC) August 14 and 8:00 AM (1500 UTC) August 14 PDT.
We apologize for the delay. VMware engineering teams are working around the clock to deliver this new version. We will continue to keep you informed of developments until this issue is fully resolved.
Please note this update is only relevant to customers who did not install the impacted release of ESX 3.5 Update 2 (build number 103908) and ESXi 3.5 Update 2 (build number 103909). If you have installed either of these please visit http://www.vmware.com/landing_pages/esxexpresspatches.html and install the express patch.
Thank you,
The VMware ESX Product Team
At 11:07 AM EST I received the FIFTH UPDATE email from VMware finally announcing the availability of the install media:
Dear VMware Customer,
We have re-issued the entire ESX/ESXi 3.5 Update 2 release (ISOs, upgrade tar and zip files, and patch bundles). They are available for download at http://www.vmware.com/download/.
Please note this update is only relevant to customers who did not install the impacted release of ESX 3.5 Update 2 (build number 103908) or ESXi 3.5 Update 2 (build number 103909). If you have installed either of these please visit http://www.vmware.com/landing_pages/esxexpresspatches.html and install the express patch.
Thank you,
The VMware ESX Product Team
Latest version numbers
From the VMTN Blog:
You may notice one oddity about the new releases. The version number that you’ll see in VirtualCenter or via the command line “vmware -v” is the version of the vmx RPM, which will be different if you applied the express patch than if you installed the reissued build. However, the build number of ESX or ESXi in the two paths is exactly the same (110268 for ESX and 110271 for ESXi). This is similar to a confusing aspect of our download pages, where we give the build number of the installer, and that number is different than the build numbers of the individual components. Think that’s confusing? We agree. As product manager MJ Lin explains in this Communities thread where she gives more details, “We are trying to move away from the build# scheme to prevent any confusion to customers.”
Alternative for Express Patch Process
At 9:12 PM on Thursday August 14 I recieved this latest email from VMware announcing a possible alternative installation process for the express patches previous released this week. I have not heard any specifics on this alternative process as of the time of this writing.
Dear VMware Customer,
This message is applicable ONLY for customers who had installed the impacted release of ESX 3.5 Update 2 (build number 103908).
We are aware that you may be encountering the following challenges installing the express patches needed to correct the problem.
• Internal change control procedures
• No available server to VMotion running VM’s onto
• Unable to schedule a maintenance window
If you have one of the challenges listed above, please contact your support provider and indicate you need assistance with the U2 Alternative Install Process (U2 AIP). An alternative installation procedure is being finalized and will be provided on an as-needed basis.
Thank you,
The VMware ESX Product Team
Posted in 
Tags: 
