-
Bug
-
Resolution: Done
-
Normal
-
4.12
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
Policies created by ACM Policy Generator do not set remediationAction at the Policy spec level
Version-Release number of selected component (if applicable):
ztp-site-generator:v4.12.0-16
How reproducible:
100%
Steps to Reproduce:
1. Configure spoke cluster using ACM PolicyGenerator according to http://registry.kni-qe-0.lab.eng.rdu2.redhat.com:3000/kni-qe/ztp-site-configs/src/sealusa2-4.12-acm-policygen/policygentemplates/spoke-0.yaml 2. Check resulting policy remediationAction oc -n ztp-site get policy spoke-0-site-config-policy -o json | jq .spec.remediationAction
Actual results:
null
Expected results:
remediationAction is set to inform, similar to the rest of the policies created by ZPT PolicyGenTemplate
Additional info:
This doesn't seem to be preventing the configuration to be applied to the spoke cluster but it'd good to have in order to have consistency across all policies. After the cluster get deployed and configured this is how the policies are reported: [kni@provisionhost-0-0 ~]$ oc get policy -A NAMESPACE NAME REMEDIATION ACTION COMPLIANCE STATE AGE spoke-0 ztp-common.common-config-policy inform Compliant 17m spoke-0 ztp-common.common-subscriptions-policy inform Compliant 17m spoke-0 ztp-group.group-du-sno-config-policy inform Compliant 17m spoke-0 ztp-site.spoke-0-site-config-policy Compliant 17m