-
Bug
-
Resolution: Done-Errata
-
Major
-
None
-
4.16.0
-
Important
-
Yes
-
False
Description of problem:
After auto remediation applied, some rules still failed for rhcos4-moderate and rhcos4-high profiles
Version-Release number of selected component (if applicable):
4.16.0 nightly + CO latest upstream version
How reproducible:
Always
Steps to Reproduce:
1. Create a custom machineconfigpool called wrscan; 2. Create a scansetting named test with wrscan role; 3. Create a ssb with rhcos4-moderate profile and test scansetting $ oc compliance bind -N test profile/rhcos4-moderate -S test 4. Trigger a rescan until all cr get applied 5. Trigger another rescan to get the final result
Actual results:
Below rules FAILED even after all autoremediation get applied: $ oc get ccr -l compliance.openshift.io/automated-remediation=,compliance.openshift.io/check-status=FAIL rhcos4-moderate-wrscan-coreos-audit-backlog-limit-kernel-argument FAIL medium rhcos4-moderate-wrscan-coreos-audit-option FAIL medium rhcos4-moderate-wrscan-coreos-nousb-kernel-argument FAIL medium rhcos4-moderate-wrscan-coreos-page-poison-kernel-argument FAIL medium rhcos4-moderate-wrscan-coreos-pti-kernel-argument FAIL high rhcos4-moderate-wrscan-coreos-vsyscall-kernel-argument FAIL medium
Expected results:
All rules with autoremediation ready should PASS
Additional info:
This issue is for 4.16 only. Not reproduced on 4.15 and 4.14.
- links to
-
RHBA-2024:138712 OpenShift Compliance Operator 1.6.0
- mentioned on