PROBLEM:
When deploying applications to Runtime Fabric using Anypoint Controller for Kubernetes [https://docs.mulesoft.com/runtime-fabric/latest/deploy-mule-app-anypoint-controller], applications may enter an unwanted or "bugged" state in Runtime Manager. These applications remain visible in the Anypoint Platform UI but are not actively deployed or manageable by standard user operations.
Attempts to delete these applications using the Anypoint Platform UI, HTTP API requests, or -> https://docs.mulesoft.com/runtime-fabric/latest/deploy-mule-app-anypoint-controller#delete-a-mule-application commands result in errors such as:
I'm not the owner...'
'uninstall: Failed to purge the release release: not found'
ROOT CAUSE:
Applications can enter an unmanageable state in Runtime Manager due to various deployment issues, such as misconfigurations, resource constraints, or inconsistencies during automated deployments. When an application reaches this specific "bugged" state, its metadata in Runtime Manager may become inconsistent with its actual state on the Runtime Fabric cluster. This inconsistency, combined with the system's current design, prevents users from forcibly deleting these applications through standard self-service mechanisms.
SOLUTION:
If you encounter applications stuck in an unwanted state in Runtime Manager that cannot be deleted using standard methods, you must contact MuleSoft Support for assistance. There is currently no self-service mechanism for users to forcibly remove applications in this specific condition.
When contacting Support, provide the following information:
1. The Anypoint Platform Organization ID where the applications are stuck.
2. The name(s) of the application(s) that need to be removed (e.g., `your-stuck-app-name`).
3. The Runtime Fabric name where the applications were deployed (e.g., `your-rtf-name`).
4. Any specific error messages received when attempting to delete the applications (e.g., `I'm not the owner...`).
5. Details about the deployment method used and steps taken so far (e.g., manual deployment, CI/CD pipeline, ArgoCD with Helm charts).
005386647

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.