vSphere IaaS Supervisor “not ready” after vCenter update

This is just a short post to mention an issue that I had today after applying an update to my Homelab’s vCenter server.

I applied the patch to take vCenter from 8.0 Update 3b to 8.0 Update 3c as I had a few updates to apply and saw that this one was waiting. The table below shows the details of these releases.

Release NameVersionRelease Date Build Number
vCenter Server 8.0 Update 3c8.0.3.003002024-10-0924305161
vCenter Server 8.0 Update 3b8.0.3.002002024-09-1724262322

The vCenter update went through well and shortly afterwards I noticed some activity in the IaaS control plane. The vCenter update clearly triggered something.

I checked back in with progress of this task after some time and saw that an issue had been flagged up.

Screenshot of the vSphere IaaS Supervisor cluster configuration update in progress.

Checking the IaaS control plane release notes didn’t immediately suggest a resolution but I had noticed that during the vCenter update the vCenter server itself had not been restarted, so I decided to give that a try.

It worked! The errors were gone and the Supervisor cluster configuration completed. I’m posting this just in case someone else hits it as an issue.

Photo by CHUTTERSNAP.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.