Namespace provides warning "Services are not accessible because this namespace is not active" from VCF Automation 9 after manually deleting VM Classes from VMware Kubernetes Services

Products

• VCF Automation
• VMware vSphere Kubernetes Service

Issue/Introduction

Issue with  accessing VMware Kubernetes Services (VKS) Supervisor Services in VCF Automation 9 via the Provider Portal > Selected Namespace  > Services > Overview.

After manually removing VM Classes from VMware vSphere Kubernetes Services (VKS) directly without detaching the VM Class from the Region Quota under Provider >  Infrastructure > Organizations > Selected Organisation > Region Quota > Reserved VM Classes.

Under  Provider Portal > Selected Namespace  > Services > Overview we see the following Warning:

Services are not accessible because this namespace is not active

VM classes shows as "N/A" within the same Overview panel.

Environment

VCF Automation 9.0.x

VMware vSphere Kubernetes Services

Cause

Discrepancy between the Database in VCF Automation 9's Tenant Manager and what is provided from VMware Kubernetes Services.

Resolution

To resolve this issue, Please open a Support Request with Broadcom Technical Support and note this Article ID (427240) in the problem description. For more information, see Creating and managing Broadcom support cases.