Hello, we have a deployment of OCP 4.13.0 with these operators: local-storage-operator.v4.13.0-202305262054 mcg-operator.v4.12.3-rhodf ocs-operator.v4.12.3-rhodf odf-csi-addons-operator.v4.12.3-rhodf odf-operator.v4.12.3-rhodf Monitoring is enabled for this setup and we were notified about noobaa-operator pod being restarted. oc get pod -n openshift-storage |grep noobaa noobaa-core-0 1/1 Running 0 12d noobaa-db-pg-0 1/1 Running 0 12d noobaa-endpoint-764f5d64fb-zvkpr 1/1 Running 0 12d noobaa-operator-57d794d8b8-mvp97 1/1 Running 16 (29h ago) 12d
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Important: Red Hat OpenShift Data Foundation 4.14.0 security, enhancement & bug fix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2023:6832