Namespaces stuck in “Configuring” after vCenter 9.1 upgrade due to missing K8s-compliant storage policy names

Products

• VMware Cloud Foundation

Issue/Introduction

• After upgrading VMware vCenter Server to version 9.1, namespaces in vSphere Supervisor Cluster may get stuck in a “Configuring” state.

• This issue is typically observed in environments with pre-existing storage policies already assigned to namespaces before the upgrade.

• vCenter UI shows alarm:

  •  "Failed to update K8s compliant names for pre-existing storage policies. Please restart WCP service once issue is resolved."

• Namespace error message:

  • Unknown error - K8s compliant name for policy {{} <policy-id>} found as nil: 1

Environment

VMware Cloud Foundation 9.1

Cause

Starting with vCenter 9.1, the Workload Control Plane (WCP) service must assign Kubernetes-compatible names to all storage policies. This update is performed during the initial service startup after the vCenter upgrade. If the WCP service is unable to communicate with the Supervisor Cluster API or the Profile-Based Management (vmware-sps) service during this initial task, the naming process fails. Because the namespaces require these compliant names to map storage policies to Kubernetes storage classes, the namespaces cannot complete their configuration.

Resolution

The issue is resolved by ensuring core service health and re-triggering the WCP initialization task.

1. Service and Health Verification:

• Ensure all Supervisor Cluster components are healthy in the vSphere Client under Workload Management > Supervisor Clusters.

• Verify the status of the SPS service on the vCenter Server Appliance:
  service-control --status vmware-sps

• If the SPS service is stopped, start it:
  service-control --start vmware-sps

2. Restart the WCP Service:

• Establish an SSH session to the vCenter Server Appliance.

• Restart the WCP service to re-initiate the storage policy naming task:
  
  service-control --stop wcp
service-control --start wcp

3. Verification:

• Confirm the namespaces transition from Configuring to Running.

• Verify the vCenter alarm is cleared automatically.

If namespaces are still stuck after completing the above steps, contact Broadcom Support for further investigation.