Error: "HA Agent cannot be installed or configured" and "Image not found" in VxRail vLCM Clusters
search cancel

Error: "HA Agent cannot be installed or configured" and "Image not found" in VxRail vLCM Clusters

book

Article ID: 432330

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

Following a vCenter Server patch in a VMware vSphere Lifecycle Manager (vLCM) enabled VxRail environment, vSphere High Availability (HA) configuration fails.

Symptoms:

- ESXi hosts report the error: "HA Agent cannot be installed or configured".


- Navigating to the vSphere Client > Cluster > Updates > Image tab displays an "Image not found" error when attempting to view or apply the desired image to the cluster.

Environment

Dell VxRail
VMware vCenter Server 8.x

Cause

The vCenter Server is unable to access the required ESXi host images located in the VxRail Manager depot.

Because vLCM cannot access the external depot, it fails to populate and validate the cluster image. Without a valid and accessible cluster image locally, the vCenter Server cannot stage and install the Fault Domain Manager (FDM) agent—the core component of vSphere HA—onto the ESXi hosts.

Resolution

To resolve this issue, the required ESXi image must be made available to the vCenter Server vLCM depot. This can be achieved using either the Download Token method or the Manual Import method.

Download Token Method

  1. Update the vSphere Lifecycle Manager download sources to include the standard Broadcom depot (dl.broadcom.com) using a customer download token.

  2. For exact instructions on generating the token and replacing the default vLCM URLs, follow Broadcom KB 390121.

Manual Import Method

  1. Download the matching ESXi host offline bundle (ZIP) for the environment from the Broadcom Support Portal.

  2. Log in to the vSphere Client and navigate to Lifecycle Manager.

  3. Manually import the downloaded offline bundle into the vCenter Server vLCM Image Depot (Action > Import Updates).

  4. Navigate to the affected Cluster > Updates > Image.

  5. Edit the cluster image and explicitly set the manually uploaded ESXi version as the desired image for the affected clusters.

  6. Save the image to allow the FDM agent VIBs to be successfully pushed to the hosts.

Powered by Wolken Software