-
Epic
-
Resolution: Done
-
Undefined
-
None
-
None
-
None
-
file-integrity-operator-1.3.6-bugs
-
Quality / Stability / Reliability
-
False
-
-
False
-
Not Selected
-
To Do
This is a placeholder epic for all bugs being delivered in file-integrity-operator-1.3.6.
- relates to
-
CMP-3658 Fileintegritynodestatus marked as failed for all the nodes after MCO update due to linkout changed for files /hostroot/etc/ipsec.d/openshift.conf and /hostroot/etc/mco/internal-registry-pull-secret.json
-
- Closed
-
-
OCPBUGS-37300 File Integrity Operator is constantly force-initializing AIDE db
-
- Closed
-
-
OCPBUGS-18933 The "re-init-on-failed" annotation will re-init db on all nodes
-
- Closed
-
-
OCPBUGS-36483 File integrity operator marks newly added node as Failed due to linkcount changed for directory /hostroot/etc/kubernetes
-
- Closed
-
-
OCPBUGS-42807 Metric file_integrity_operator_node_failed of file integrity operator reset after pod restart
-
- Closed
-
- links to