-
Bug
-
Resolution: Done-Errata
-
Major
-
None
-
4.13
-
No
-
False
-
Description of problem:
After removing a profile from a done scan in ScanSettingBinding, compliance operator does not remove old scans, and when launching new SSB with deleted profile, it fails to update the result.
Version-Release number of selected component (if applicable):
Compliance Operator v1.4.0
How reproducible:
Always
Steps to Reproduce:
1. Launch a SSB with ocp4-pci-dss and ocp4-cis
2. Wait for scan to finish and remove ocp4-cis from the SSB
3. Create another SSB with only ocp4-cis
Actual results:
The new SSB show old result from old SSB
Expected results:
The new SSB show new compliance check result
Additional info:
- links to
-
RHBA-2024:129828
openshift-compliance-operator bug fix and/or enhancement update
- mentioned on
