-
Bug
-
Resolution: Unresolved
-
Major
-
MCE 2.11.0
-
Quality / Stability / Reliability
-
False
-
-
False
-
-
-
Important
-
None
Description of problem:
When enabling any of the CAP components (CAPI, CAPA, CAPOA, CAPM3, CAPZ), their respective namespaces are stuck in Terminating status. The only finalizer I see is "kubernetes".
After some more analysis, this turns out to be related to ASO and some Azure CRDs that are left over if CAPZ was enabled.
Version-Release number of selected component (if applicable):
"acm_image": "quay.io:443/acm-d/acm-dev-catalog:2.16.0-DOWNSTREAM-2026-01-28-11-30-47",
"mce_image": "quay.io:443/acm-d/mce-dev-catalog:2.11.0-DOWNSTREAM-2026-01-28-08-48-45",
How reproducible:
Always
Steps to Reproduce:
- Enable any CAP component listed above
- Disable it
Actual results:
The namespace remains and is stuck in Terminating status.
Expected results:
The namespace should be deleted.
- blocks
-
ACM-18636 Onboard CAPZ into MCE 2.11
-
- Review
-