Stale OpenStack Regions in PCD
Problem
Old OpenStack regions and endpoints still exist even after the PCD region is deleted.
Environment
Private Cloud Director Virtualization
Self-Hosted Private Cloud Director Kubernetes
Cause
This is a known issue and a bug: PCD-2664 has been raised to track this matter.
CAUTION
Do not create/delete an OpenStack region in PCD.
To create/delete a PCD region:
PCD SaaS Users: Contact Platform9 Support
PCD Self-Hosted Users: Follow the airctl region creation/deletion process.
Diagnostics
Get the region list using the command given below, and see the stale region entry.
Check if there are any endpoints available for the stale region.
Workaround
Proceed with extreme caution. The steps below are non-recoverable and could result in a complete system outage.
Always double-check the region ID before deletion to avoid affecting active deployments.
This operation is safe and non-disruptive if performed correctly.
NOTE: DO NOT PERFORM THE DELETE OPERATION ON ANY WORKING REGION.
Delete all endpoints associated with a given stale region, modify the script below using the stale region name, then execute it to remove the endpoints.
Verify if there is any endpoint available for the stale region.
Once all stale endpoints associated with a given stale region are removed. Perform the region delete operation.
Delete all endpoints in the stale region first, or will encounter the issue below.
Failed to delete region with ID '[STALE_REGION_NAME]': Unable to delete region [STALE_REGION_NAME] because it or its child regions have associated endpoints. (HTTP 403) (Request-ID: [req_id])
Validation
Validate if the stale region is deleted, the below command should not show any stale region information.
Last updated
