After failed Supervisor cluster deployment in vCenter, attempts to 'deactivate' result in a loop in tasks between "apply solution" and "delete solution".

Products

• VMware vSphere Kubernetes Service

Issue/Introduction

After failed Supervisor cluster deployment in vCenter, attempts to 'deactivate' result in a loop in tasks between "apply solution" and "delete solution".

The Supervisor IP/DNS details were input incorrectly (Wrong Name/IP/etc.). 

Environment

vSphere/VKS 8.x, 9.x

Cause

The initial deployment failed due to invalid network entries preventing DNS resolution. When deactivation was triggered via the UI, an active deployment task was still held in the vCenter Server Task Manager state table. The overlapping cleanup task triggered a lock conflict, causing the task scheduler to cycle between apply and delete states while attempting to clean up a non-existent solution object.

Resolution

 

1. Perform a graceful reboot of the active vCenter Server Appliance (vCSA) to clear stale runtime tasks and unlock the cluster entity.

2. Verify that all vCenter Server core services have started successfully.

3. Access vCenter > Supervisor Management and re-attempt the Deactivate process if the failed Supervisor state persists.

4. Re-initiate Supervisor deployment using the correct IP addresses, hostnames, and accessible DNS configurations for the intended disconnected network segment.