Supervisor remains in a Configuring state with a 404 Not Found error

Products

• VMware vSphere Kubernetes Service
• VMware vCenter Server

Issue/Introduction

• After a vCenter Server upgrade to 9.1, the Supervisor Cluster and its namespaces remain in a persistent "Configuring" state, as below: 
  
  
  
  
• The vCenter Server Content Library Service logs (cls) and Workload Control Plane management (wcp) write repeated NotFound exceptions:
  
  
  • /var/log/vmware/content-library/cls.log

errorType = NOT_FOUNDdefaultMessage = Library <Library-UUID> not found.,args = [<Library-UUID>],id = com.vmware.vdcs.cls-main.library_not_found
    
    
  • /var/log/vmware/wcp/wcpsvc.log the following specific failure is observed during the image registry reconciliation phase:
    
    Error while adding library usage (urn: urn:vmomi:supervisor:<Supervisor-UUID>) on content library <Library-UUID> for supervisor: err: GET http://localhost:1080/api/content/library/<Library-UUID>/usages: 404 Not Found

Environment

• VMware vCenter Server 9.1

• VMware vSphere Kubernetes Service (VKS) 9.1

Cause

The Workload Control Plane (WCP) service attempts to reconcile and register usage records for every Content Library listed in the supervisor_content_source_configs metadata. If this configuration contains stale or orphaned library UUIDs that no longer exist in the vCenter Content Library Service (CLS), internal API calls to retrieve library usages return a 404 Not Found error.

The WCP service enters an infinite reconciliation loop while attempting to process these invalid entries. This prevents the Supervisor Cluster and its Namespaces from successfully transitioning out of the Configuring state.

Resolution

To work around this issue, remove the stale library reference from the Supervisor configuration:

1. Identify the UUID of the content library causing the 404 error from the vSphere Client, wcpsvc.log, or cls.log.

2. Open an SSH session to the vCenter Server.

3. Use the DCLI to unassign the specific library by running the following command: dcli com vmware vcenter namespacemanagement lifecycle content libraries unassign --library <Problematic-Library-UUID>

4. Monitor the environment to verify that automatic reconciliation completes and the Supervisor state returns to a Running state.

5. If the Supervisor remains in a Configuring state, unassign all current libraries via the vSphere Client (Navigate to Supervisor Management > Supervisor > Select the affected Supervisor > Configure > General > Kubernetes Service).

6. Remove and add the active Content Library.

7. Restart the WCP service to force a metadata refresh by running the following command: service-control --restart wcp or via VAMI 

Note: Unassigning or reassigning metadata-only library references does not delete existing virtual machine disks on ESXi hosts or disrupt running workloads. While the WCP service restarts, you cannot deploy new clusters or modify Supervisor settings.