Description of problem:
If I have a Policy with a Configuration Policy and I later rename that Configuration Policy, the old named Configuration Policy will remain even after the new named Configuration Policy is created.
Another scenario is if you have a Policy with two Configuration Policies and I later remove one of them, the removed Configuration Policy will stay on the managed cluster but no status will be reported back to the Policy.
The workaround is disable the Policy and reenable it or to delete the entire Policy.
Version-Release number of selected component (if applicable):
All ACM versions.
How reproducible:
Very reproducible
Steps to Reproduce:
- See the above scenarios
Actual results:
The policy templates are left behind.
Expected results:
The policy templates are removed from the cluster when they are removed from the Policy.
- causes
-
ACM-3879 governance-policy-framework pod crashlooping on managed cluster
- Resolved