Merge pull request #70153 from GroceryBoyJr/known-issue-co

OCPBUGS-7355: Some rules will FAIL after auto remediation applied

Author: bscott-rh

security/compliance_operator/compliance-operator-release-notes.adoc

@@ -38,6 +38,8 @@ The following advisory is available for the OpenShift Compliance Operator 1.4.0:
 [id="compliance-operator-1-4-0-bug-fixes"]
 === Bug fixes
 
+* Previously, on a cluster with Windows nodes, some rules will FAIL after auto remediation is applied because the Windows nodes were not skipped by the compliance scan. With this release, Windows nodes are correctly skipped when scanning. (link:https://issues.redhat.com/browse/OCPBUGS-7355[*OCPBUGS-7355*])
+
 * With this update, `rprivate` default mount propagation is now handled correctly for root volume mounts of pods that rely on multipathing. (link:https://issues.redhat.com/browse/OCPBUGS-17494[*OCPBUGS-17494*])
 
 * Previously, the Compliance Operator would generate a remediation for `coreos_vsyscall_kernel_argument` without reconciling the rule even while applying the remediation. With release 1.4.0, the `coreos_vsyscall_kernel_argument` rule properly evaluates kernel arguments and generates an appropriate remediation.(link:https://issues.redhat.com/browse/OCPBUGS-8041[*OCPBUGS-8041*])
@@ -72,6 +74,11 @@ This update addresses a CVE in an underlying dependency.
 To enable FIPS mode for your cluster, you must run the installation program from a {op-system-base} computer configured to operate in FIPS mode. For more information about configuring FIPS mode on RHEL, see link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/security_hardening/assembly_installing-the-system-in-fips-mode_security-hardening[Installing the system in FIPS mode].
 ====
 
+[id="compliance-operator-1-3-1-known-issue"]
+=== Known issue
+
+* On a cluster with Windows nodes, some rules will FAIL after auto remediation is applied because the Windows nodes are not skipped by the compliance scan. This differs from the expected results because the Windows nodes must be skipped when scanning. (link:https://issues.redhat.com/browse/OCPBUGS-7355[*OCPBUGS-7355*])
+
 [id="compliance-operator-release-notes-1-3-0"]
 == OpenShift Compliance Operator 1.3.0