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

[2.12] panic in config-policy uninstallation pod

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • ACM 2.12.6
    • None
    • GRC
    • None
    • Quality / Stability / Reliability
    • 1
    • False
    • Hide

      None

      Show
      None
    • False
    • Hide
      Previously, ConfigurationPolicies that had no annotations could cause the controller to crash when disabling or uninstalling the policy addon. Now, the controller is stable throughout the process.

      The issue can also be worked around without updating by ensuring all ConfigurationPolicies on the managed cluster have an annotation, by manually applying one as needed.
      Show
      Previously, ConfigurationPolicies that had no annotations could cause the controller to crash when disabling or uninstalling the policy addon. Now, the controller is stable throughout the process. The issue can also be worked around without updating by ensuring all ConfigurationPolicies on the managed cluster have an annotation, by manually applying one as needed.
    • GRC Sprint 2025-16
    • Important
    • None

      Description of problem:

      When removing the config-policy-controller addon from a managed cluster (or as part of a complete uninstallation of ACM), the `config-policy-controller-uninstall` pod created as part of the addon pre-delete task may panic:

      I0131 18:34:55.991371       1 triggeruninstall.go:35] Setting the Deployment uninstall annotation
I0131 18:34:56.011706       1 triggeruninstall.go:76] Checking if the uninstall preparation is complete
panic: assignment to entry in nil map
goroutine 1 [running]:
open-cluster-management.io/config-policy-controller/pkg/triggeruninstall.TriggerUninstall({0x3a61470, 0xc00078a0e0}, 0xc000479b08, {0x7ffd059752ed, 0x18}, {0x7ffd0597531d, 0x23}, {0xc0006700e0, 0x2, 0x2})
 /go/src/github.com/stolostron/config-policy-controller/pkg/triggeruninstall/triggeruninstall.go:101 +0x90a
main.handleTriggerUninstall()
 /go/src/github.com/stolostron/config-policy-controller/main.go:715 +0x6a5
main.main()
 /go/src/github.com/stolostron/config-policy-controller/main.go:115 +0x75

       

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

      2.13

      How reproducible:

      Steps to Reproduce:

      1. create a configurationpolicy with `DeleteAll`
      2. disable the config-policy addon on the managed cluster
      3. check the uninstall pod

      Actual results:

      CrashLoopBackOff

      Expected results:

      Successful removal of the addon.

      Additional info:

      This seems new to 2.13

              jkulikau@redhat.com Justin Kulikauskas
              jkulikau@redhat.com Justin Kulikauskas
              Derek Ho Derek Ho
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: