vCenter Supervisor Management is Blank

vCenter Supervisor Management is Blank

Enabling / Disabling Supervisor Management Errors

The Issue?

Enabling or disabling supervisor management in vCenter may result in a partially configured cluster, where you see the namespace creation and the SuperVisorControlPlaneVM deployed.

However, under Supervisor Management, the supervisor is not listed and you see the below errors in vCenter.

You can see the below error in the var/log/vmware/wcp/wcpsvc.log.

error wcp [kubelifecycle/pman_client.go:397] [opID=XXXXXXXXX:Enable:domain-cXX] supervisor content is being processed
error wcp [content/catalog.go:863] [opID=XXXXXXXXX:Enable:domain-cXX] catalog is not ready

The Workaround

This issue seems to surface when assigning a local content library for vSphere Kubernetes Service (VKS) because an unknown content library / content library item was associated with the WCP service. Resulting in a WCP service crash and never being able to start. I am not entirely sure why this is the case as it was a simple content library, however the below steps resolved the issue.

1. SSH into vCenter as root and run “sudo -u wcp /opt/vmware/vpostgres/current/bin/psql --username wcpuser --dbname VCDB --host /var/run/vpostgres“

2. select * from supervisor_content_source_configs;

3. From the output find t he ID and run “DELETE FROM supervisor_content_source_configs WHERE id=6;” – Change the ID to suit your environment, it is from the first column in the select command.

4. Restart the WCP service with “vmon-cli --restart wcp“

As you can see below, the supervisor management page now shows the supervisor cluster and enters a running state.

Related