This morning the VMware’s customers that upgraded their virtual data centers with the new Infrastructure 3.5 Update 2 (build 103908) had an awful surprise: any virtual machine that is turned off cannot be powered on again, and any attempt to execute a VMotion (the live migration of a VM from one host to another) fails.
The reason behind this huge and unprecedented issue is an error in the license expiration time.
The only way to workaround the problem at the moment is to disable the Network Time Protocol (NTP) client and set the date back to August 10, as promptly suggested by a customer here.
Of course this countermeasure has an impact on the log consistency and on any tool that analyzes the VirtualCenter events for different purposes (performance monitoring, trend analysis, capacity planning calculation, etc.).
More than that obviously, this issue has an impact on the availability of those infrastructures where the IT administrators are in vacation (and there are many on August 12) and cannot operate any recovery.
The users from all around the world are reporting failures of part of their systems and in some case even the complete knock-down.
VMware has over 200,000 enterprise customers (100% of Fortune 100 and 95% of Fortune 500), and it claimed that 59% of them use VMotion in production.
The company didn’t provide any statistics about how many already deployed the Update 2, but the license fault could have impacted thousands of them.
VMware is aware of the issue but couldn’t provide any immediate solution.
At the moment it seems that the entire VMware Knowledge Base collapsed.
Calling the support line customers can just receive a brief message saying that the problem will be solved within 36 hours.
Additionally, VMware removed the capability to download any affected product.
The existence of such issue is more than enough to undermine the credibility of the company (which already made some mistakes in the past) in a complex moment of its successful history.
A 36 hours timeframe to provide a solution is just an unacceptable answer for all those enterprises that deploy virtualization in production.
The whole thing may severely damage the stock performance of today.
Update: The license of VMware ESXi 3.5 U2 (build 103909) is reported as affected by the same problem.
Second update: To further aggravate the situation, today is the so called Microsoft Patch Tuesday, so a number of guest operating systems are being automatically (or manually for those unaware of the issue) rebooted.
As this is not enough, any customer running a VDI environment certainly allows its end-users to reboot their virtual desktops any time they want.
Third update: as the VMware Knowledge Base is still unavailable probably due to overload, virtualization.info publishes the original KB article about this issue.
Fourth update: The issue also impacts ESX 3.5 Update 1 with certain patches.
The full details are available in the comment section of this post, thanks to the effort of a virtualization.info reader.
Suddenly the problem is no more a matter of early adoption.
Fifth update: As promptly reported in the comments section, the VMware’s new CEO, Paul Maritz, published on the official blog an apology, informing that a patch has been released:
…I am sure you’re wondering how this could happen. We failed in two areas:
- Not disabling the code in the final release of Update 2
- Not catching it in our quality assurance process
We are doing everything in our power to make sure this doesn’t happen again. VMware prides itself on the quality and reliability of our products, and this incident has prompted a thorough self-examination of how we create and deliver products to our customers. We have kicked off a comprehensive, in-depth review of our QA and release processes, and will quickly make the needed changes…
Maritz couldn’t desire a worst start for its new role in the company. Nonetheless this is a great opportunity: the co-founder and former VMware CEO, Diane Greene, was often accused of being unable to grow her company as a big enterprise, capable of competing against Microsoft.
Handling this incident Maritz has the first chance to demonstrate that he’s the right person to do better than Greene.
Sixth update: VMware is still unable to republish the ESX 3.5 and ESXi 3.5 Update 2 images for fresh installations.
Their availability is expected by August 13, 2008 at 6pm PST.
Seventh update: VMware just informed its customers that it cannot deliver a new, patched image of the product for the planned deadline.
The images are now planned for release August 14, between 2am and 8am PDT.
Eighth update: A number of enterprise customers may be unable to apply the first patch released (see Fifth update above) for a number of reasons:
- Unable to schedule a maintenance window
- Internal change control procedures
- No available server to VMotion running VM’s onto
VMware is aware of these constrain and informed its customers that is developing a second procedure, called U2 Alternative Install Process (U2 AIP), to apply the patch, available on demand calling the Support.
At the moment (August 15, 2008) there is no release date for this new patch installation procedure.
Meanwhile the full patched images are finally available online and all the download links have been reactivated.
The new build numbers are:
- ESX 3.5 Update 2 – 110268
- ESXi 3.5 Installable Update 2 – 110271