VKS Supervisor not showing up as an option in Region Quota

Products

• VCF Automation

Issue/Introduction

This issue is caused by a data inconsistency between the VCFA (VMware Cloud Foundation 9 - Automation) and VC (vCenter) environments. The sequence of events leading to this is typically:

1. A region was created in VCFA and associated with a specific VKS Supervisor.

2. Later, that VKS Supervisor was deleted directly within VC.

3. A new VKS Supervisor was then created in VC.

4. The original region entity in VCFA was not updated or removed, so it still holds a "stale" reference to the old, deleted supervisor.

Because the region configuration points to a non-existent supervisor, the system cannot correctly associate the new supervisor with it, making it unavailable during Region Quota creation.

 

Cause

Customer created a region with supervisor in VCFA. Later, in VC, they deleted the supervisor and created new one without cleaning the region entity in VCFA.

Resolution

To resolve this issue, you must remove the stale region configuration and create a new one that correctly points to the active VKS Supervisor.

1. Delete the Stale Region: In the VCFA environment, identify and delete the region that is associated with the old, deleted supervisor.
2. Create a New Region: Create a new region in VCFA.
3. Associate the New Supervisor: During the creation process, associate the new region with the current, active VKS Supervisor.
4. Verify the Fix: Navigate back to the Region Quota configuration screen. You should now see the new VKS Supervisor as an available option, allowing you to create the quota successfully.