Message important et urgent concernant l'upgrade ESX(i) 3.5 - ISOs corrigés disponibles + Procedure de MAJ manuelle

[oparcollet]

Les nouveaux ISOs sont disponible sur depuis ce soir 17h00.

IL NE FAUT PAS LES INSTALLER PAR DESSUS UNE 3.5u2 DEJA CORRIGEE AVEC L'EXPRESSPATCH.

En bootant sur le CD, il est possible de procéder directement à la mise à jour de la 3.5u2 non patchée.

-

---

Quelques informations complémentaires

Un timebomb, se déclenchant le 12 août, a été oublié lors de la compilation de la ESX(i)3.5u2.

Les correctifs sont diponibles ICI :

• ESXi 3.5:[http://www.vmware.com/go/esxiu2patch081208]

• ESX 3.5 :

Dear VMware Customers,

Please find the latest update about the product expiration issue. From this point on, we'll provide an update every two hours. Thanks.

Problem:

An issue has been discovered by many VMware customers and partners with ESX/ESXi 3.5 Update 2 where Virtual Machines fail to power on or VMotion successfully. This problem began to occur on August 12, 2008 for customers that had upgraded to ESX 3.5 Update 2. The problem is caused by a build timeout that was mistakenly left enabled for the release build.

Affected Products:

• VMware ESX 3.5 Update 2 & ESXi 3.5 Update 2

• Reports of problems with ESX 3.5 U1 with the following 3.5 Update 2 patch applied.
  1. ESX350-200806201-UG

• No other VMware products are affected.

What has been done?

• Product and Web teams pulled the ESX 3.5 Update 2 bits from the download pages last night so no more customers will be able to download the broken build.

• VMware Engineering teams have isolated the cause of the problem and are working around the clock to deliver updated builds and patches for impacted customers.

• A Knowledgebase article has been published ( ), but traffic to the knowledgebase is causing time outs. A new static page has been published at that customers and partners will be able to view.

• The phone system has been updated to advise customers of the problem

• Vmware partners have been notified of the issue.

Workarounds:

1. Do not install ESX 3.5 U2 if it has been downloaded from VMware's website or elsewhere prior to August 12, 2008.

2. Set the host time to a date prior to August 12, 2008. This workaround has a number of very serious side affects that could impact product environments. Any Virtual Machines that sync time with the ESX host and serve time sensitive applications would be broken. These include, but are not limited to database servers, mail servers, & domain administration systems.

Next Steps:

VMware to notify customers who have downloaded this version and provide an update every two hours.

Resolution:

VMware Engineering has isolated the root cause and is working to produce an express patch for impacted customers today. The target timeframe is 6pm, August 12, 2008 PST.

FAQ:

1. What would this express patch do?
   
   More information will be provided in subsequent communication updates.

2. Will VMware still reissue the upgrade media and patch bundles in the timeframe that has been communicated?
   
   Yes. We still plan to reissue upgrade media by 6pm, August 13 PST (instead of noon, August 13 PST) and all update patch bundles later in the week. We will provide an ETA for the update patch bundles subsequently. NOTE: the "patch bundles" referred to here are for the patches listed above under "Affected Products" and the other bundles released at GA. They are not the same as the express patch which is targeted for 6pm, August 12, 2008 PST as stated above.

3. Why does VMware plan to reissue the upgrade media before the patch bundles? That is a wrong priority call!
   
   This is not a matter of priority. Since we can get done building and testing the upgrade media before the patch bundles, we want to make that available to customers first instead of reissuing all the binaries later in the week.

4. Can VMware issue a patch that opens the licensing backdoor in the next hour as a critical measure?
   
   There is no licensing backdoor in our code.

5. Does this issue affect VC 2.5 Update 2?
   
   No.

6. What is VMware doing to make sure that the problem won't happen again?
   
   We are making improvements on all fronts. The product team had endeavored to deliver a release with support customers deem important. But we fell short and we are deeply sorry about all thedisruption and inconveniences we have caused. We have identified where the holes are and they will be addressed to restore customers' confidence.

[InterPC]

Bonjour,

Avez-vous réussi à installer ce patch ?

Avec VMware Infrastructure Manager, si je prends la fonction Check Now, le téléchargement se passe bien, mais il se termine toujours par la fenêtre "Downloaded package's did not pass integrity check", et si je passe par la fonction Add Files dans Package Cache, j'ai une fenêtre "Invalid Update Bundle"...:<((((

Je suis sur un ESX3i version 3.5.0 build-103909 qui, si je n'avais pas pris du retard la semaine dernière, devait entrer en production le vendredi 8 août...:<(((

[oparcollet]

Bonjour,

Le patch fonctionne.

Pour pallier à tout problème, voici une méthode sûre pour appliquer le patch manuellement.

ATTENTION, CELA IMPLIQUE UN REBOOT.

Pour ma part, ayant deux fermes HA,DRS,VMOTION reliées à un stockage mutualisé, j'ai appliqué le patch directement à partir de la console de mes serveurs via SSH :

Après avoir copié le patch ESX350-200806812-BG.zip et l'avoir dézzipé dans le DATASTORE commun aux serveurs, je me suis placé dans ce dernier et je l'ai appliqué en faisant un esxupdate update.

Si le serveur ESX est isolé et n'a pas accès à un stockage mutualisé, Il est possible de désactiver provisoirement le firewall afin de transférer le fichier via FTP en local

à partir de la console taper :

-> esxcfg-firewall -allowIncoming

-> esxcfg-firewall --allowOutgoing

-> mkdir /patch

-> cd patch

-> ftp -i (serveurftp)

-> mget ESX350*

-> bye

-> unzip ESX350-200806812-BG.ZIP

-> cd ESX350-200806812-BG

-> esxupdate update

-> shutdown -r now

Un reboot pour tout mettre au clair et c'est OK.

Bon courage.

[InterPC]

Bonjour,

Merci pour cette manip.

Mais en fait, il semble que cela venait d'un problème de compatibilité avec le client Vmware Infrastructure Update. En le réinstallant, cela a bien fonctionné normalement.

Cordialement