-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
None
-
Quality / Stability / Reliability
-
1
-
False
-
-
False
-
-
-
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:
- create a configurationpolicy with `DeleteAll`
- disable the config-policy addon on the managed cluster
- check the uninstall pod
Actual results:
CrashLoopBackOff
Expected results:
Successful removal of the addon.
Additional info:
This seems new to 2.13
- clones
-
-
- Closed
-