Library not found error when deploying vSphere Supervisor 9.0

Products

• VMware vSphere Kubernetes Service

Issue/Introduction

• Deploying vSphere Supervisor 9.0 results in the following error:

  

• Content library logs on the vCenter Server under /var/log/vmware/content-library/cls.log report:

 error wcp [content/controller.go:303] [opID=cl-<content library id>] Error creating library processor while processing CL: <content library id>, error: Library not found error
 debug wcp [content/repository.go:214] [opID=cl-<content library id>] Updated stateVector for CL: <content library id> to state: APPLY, phase: ERROR, status: ERROR

Environment

• vSphere Supervisor 9.0
• VMware Cloud Foundation (VCF) 9.x
• vCenter Server 9.x

Cause

The vCenter database (VCDB) retains a stale reference in the supervisor_content_source_configs table. If the Content Library is removed from inventory before being unassigned from vSphere Namespaces (WCP), the system continues to attempt reconciliation with the deleted UUID, preventing a fallback to the embedded image.

Resolution

This issue is resolved in VMware vSphere Supervisor 9.0.0.0100 and higher. See Download Broadcom products and software for steps to download this release.

To workaround the error in your current environment, manually unassign the orphaned library using the Data Center CLI (DCLI):

1. Open an SSH session to the vCenter Server and log in as root.

2. Enable the shell with the command: shell

3. Enter the interactive DCLI prompt: dcli +i

4. Provide local administrator credentials, such as [email protected].

5. Run the following command to remove the stale library association: com vmware vcenter namespacemanagement lifecycle content libraries unassign --library <content library id>

6. Restart the vSphere Supervisor configuration from the vSphere Client.