Unable to delete failed AEM Cloud Manager development environment and credit not released
Learn how to resolve issues where a failed AEM Cloud Manager development environment can’t be deleted and the associated credit isn’t released.
Description description
Environment
Adobe Experience Manager (AEM) Cloud Manager Development environments
Symptoms
- A development environment creation fails due to insufficient capacity in the selected region.
- The environment remains in a Failed state and can’t be deleted through the Cloud Manager UI or API.
- No resources or Kubernetes namespaces were provisioned for the failed environment.
- The associated development environment credit isn’t released, preventing the creation of new development environments.
Cause
This issue occurs when the environment creation fails before any resources or namespaces are provisioned. As a result, the environment can’t be deleted, and the credit remains consumed.
Resolution resolution
Follow the steps below to resolve the issue:
-
Confirm that the environment is stuck in the Failed state and can’t be deleted through Cloud Manager (UI or API).
-
Check that no Author/Publish pods or Kubernetes namespaces were ever provisioned for this environment.
-
In Cloud Manager, verify that the development environment credit is still marked as consumed by the failed environment.
-
If the environment can’t be deleted and the credit isn’t released, contact Adobe Support for assistance. When submitting your request, provide the following information:
-
The name of the failed environment
-
The program identifier
-
The environment identifier
-
-
After Adobe Support completes remediation, confirm that the environment no longer appears in Cloud Manager and that the development credit is available for reuse.
-
Attempt to create a new development environment to verify that the credit has been restored.