Uploaded image for project: 'Red Hat Advanced Cluster Management'
  1. Red Hat Advanced Cluster Management
  2. ACM-29179

CAP namespaces stuck in Terminating status

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • MCE 2.11.0
    • MCE 2.11.0
    • capi
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • 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:

      1. Enable any CAP component listed above
      2. Disable it

      Actual results:

      The namespace remains and is stuck in Terminating status.

      Expected results:

      The namespace should be deleted.

              mveber@redhat.com Marek Veber
              rh-ee-msmigiel Matthew Smigielski
              ACM QE Team
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: