Chris Hall bio photo

Chris Hall

Making technology fit my requirements...

Windows, Linux, Virtualisation, Unified Computing & Cloud Offerings Design Engineer.

PolarCloudsUK Chris LinkedIn Github

Old vSphere Logo Patching lab and production vCenters this fault often pops up and every time it does it does give me the one of those terrible heart stopping moments.

You’d think with an error this bad, it would be the end of your vCenter server, time to start looking round for some vCenter installation files right?

Wrong! (phew)

Here is a screenshot of the error so you can enjoy the terror too:

OMG!

A closer view for your delectation:

OMG! Close Up

Update installation failed, vCenter is non-operational

Don’t panic! Simply carry on and patch vCenter using the workaround below. No rebuild necessary. :sunglasses::thumbsup:

The Workaround

Here’s how I update vCenter. In my experience this method allows for a much smoother patch experience.

First step: BACKUP!! You do backup your vCenter don’t you? (HERE you go) :wink:

Next, check for free disk space on the vCenter server. SSH to vCeneter, open shell and issue the df -h command:

vC df -h

From there, exit shell and enter back into the appliance shell (see VMware KB2100508 for vCenter shell details and toggling between them).

Mount the vCenter patch ISO file via a VMRC session to the vCenter VM initiated from the ESXi server currently running vCenter server.

To stage the packages in the update ISO:

software-packages stage --iso

Accept the licence agreement. To list the staged content:

software-packages list --staged

Finally, kick off the patch install:

software-packages install --staged

All of which looks like this in practice:

Patching vC

Once done, exit SSH session and reboot vCenter via the console:

Reboot vC

Unmount the ISO and it’s job done. Much easier on the heart! :sparkling_heart::sunglasses::thumbsup:

-Chris