After a vCenter update or upgrade, vSphere HA repeatedly goes into a "Retrying" and "Uninitialized" state but self-remediates.

Products

• VMware vCenter Server
• VMware vCenter Server 7.0
• VMware vCenter Server 8.0

Issue/Introduction

The "Configuring vSphere HA on the cluster" task fails after a vCenter Server update or upgrade but eventually automatically self-remediates.

Environment

VMware vCenter Server

Cause

When the vCenter is updated or upgraded, the FDM agent on the ESXi hosts is updated as well.

Resolution

This vSphere HA process is expected behavior and by design.

Single-Image Cluster

• The cluster image will be updated with the new vSphere HA (FDM) solution. Once completed, vSphere Lifecycle Manager will install the FDM VIB on the ESXi hosts in the cluster, and the vSphere HA election will occur.

Non Single-Image Cluster (ie: Baselines)

• The vCenter is responsible for getting the new FDM agent onto the ESXi hosts to update them.

The difference between a Non-Single-Image and Single-Image managed cluster is just the matter of which service is responsible for getting the FDM VIB installed on the ESXi hosts.

It is a similar process for both clusters as this can happen after a vCenter update/upgrade, and vSphere HA elections may be seen.