Skip to content

Commit f5396e0

Browse files
authored
Merge pull request #96654 from stevsmit/136-fio-add
Adds 136 FIO rns
2 parents 69b41c0 + fab596f commit f5396e0

File tree

1 file changed

+0
-2
lines changed

1 file changed

+0
-2
lines changed

security/file_integrity_operator/file-integrity-operator-release-notes.adoc

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,6 @@ For an overview of the File Integrity Operator, see xref:../../security/file_int
1515

1616
To access the latest release, see xref:../../security/file_integrity_operator/file-integrity-operator-updating.adoc#olm-preparing-upgrade_file-integrity-operator-updating[Updating the File Integrity Operator].
1717

18-
////
1918
[id="file-integrity-operator-release-notes-1-3-6"]
2019
== OpenShift File Integrity Operator 1.3.6
2120

@@ -35,7 +34,6 @@ The following advisory is available for the OpenShift File Integrity Operator 1.
3534
* Previously, the Advanced Intrusion Detection Environment (AIDE) daemonset pods would constantly force-initialize the AIDE database. With this release, FIO initializes the AIDE database only once. (link:https://issues.redhat.com/browse/OCPBUGS-37300[*OCPBUGS-37300*])
3635

3736
* Previously, some link paths in the Machine Config Operator (MCO) configuration, such as `/hostroot/etc/ipsec.d/openshift.conf` and `hostroot/etc/mco/internal-registry-pull-secret.json`, were modified during an MCO update. This led to failed file integrity checks on nodes after the update, which disrupted user experience. With this update, the modified file link paths in the MCO configuration have been updated. File integrity checks now pass after an update, helping to ensure a stable cluster. (link:https://issues.redhat.com/browse/OCPBUGS-41628[*OCPBUGS-41628*])
38-
////
3937

4038
[id="file-integrity-operator-release-notes-1-3-5"]
4139
== OpenShift File Integrity Operator 1.3.5

0 commit comments

Comments
 (0)