Supervisor Cluster stuck in Configuring state with the following error "Configured Control Plane VMs API request to VMware ESX Agent Manager (eam) failed. Details 'ServerFaultCode: "com.vmware.eam.DisabledOperationException""

Products

• VMware vSphere Kubernetes Service

Issue/Introduction

• Supervisor Cluster is stuck in Configuring state with the following error message on the UI : 
  

  Configured Control Plane VMs API request to VMware ESX Agent Manager (eam) failed. Details 'ServerFaultCode: "com.vmware.eam.DisabledOperationException: Invocation of disabled API Agent.markAsAvailable"

  

• The Supervisor Cluster remains unaffected, with all nodes and pods in a Running state and reporting as Healthy.  

Environment

VMware vSphere Kubernetes Service

Cause

This issue occurs when the cluster’s agencies remain disabled in EAM, typically after running the vSAN Shutdown Wizard without subsequently using the Restart Cluster Wizard, which is responsible for re-enabling the EAM agencies.

Resolution

Please follow the steps outlined in the Resolution section of the KB article - vCLS VMs do not deploy due to the EAM Agency showing as "Disabled" following a vSAN Cluster Shutdown.

Upon completion, the Supervisor Cluster should appear in a Healthy state