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

Edge Manager leaves behind DB migration pod and PVC

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • ACM 2.15.0
    • Installer
    • None
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • False
    • Installer Sprint 2025-70
    • Important
    • None

      Description of problem:

      When disabling edge-manager, the "flightctl-db-migration" pod remains as well as the PVC "flightctl-alertmanager-data-flightctl-alertmanager-0". If you then enable edge-manager again, it will create a new DB migration pod and will keep doing so every time you enable and disable the component.

      Similarly, the following resources also do not get cleaned up when the component is disabled:
      ClusterRole: flightctl-client
      ClusterRoleBinding: flightctl-agent-registration, flightctl-client

      Version-Release number of selected component (if applicable):

      "acm_image": "quay.io:443/acm-d/acm-dev-catalog:2.15.0-DOWNSTREAM-2025-10-08-15-13-27",
      "mce_image": "quay.io:443/acm-d/mce-dev-catalog:2.10.0-DOWNSTREAM-2025-10-09-01-16-59",

      How reproducible:

      Always

      Steps to Reproduce:

      1. Install the build above.
      2. Toggle edge-manager-preview a few times.

      Actual results:

      The pod and PVC should be deleted upon disabling of the component.

      Expected results:

      The pod gets created repeatedly and the PVC remains.

              cwall@redhat.com Cameron Wall
              rh-ee-msmigiel Matthew Smigielski
              Matthew Smigielski Matthew Smigielski
              ACM QE Team
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: