Bug 2216401

Summary: ]backport to 4.13.z] noobaa-operator pod shows multiple restarts
Product: [Red Hat Storage] Red Hat OpenShift Data Foundation Reporter: Nimrod Becker <nbecker>
Component: Multi-Cloud Object GatewayAssignee: Nimrod Becker <nbecker>
Status: CLOSED ERRATA QA Contact: Tiffany Nguyen <tunguyen>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.13CC: dzaken, kbg, kmanohar, kramdoss, nbecker, ocs-bugs, odf-bz-bot, sasha, sdymnik
Target Milestone: ---   
Target Release: ODF 4.13.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 4.13.1-3 Doc Type: Bug Fix
Doc Text:
Previously, there were repeated crashes of the MultiCloud Object Gateway (MCG) Operator because the operator collided with the updates to the structure when it was trying to print a debug message regarding an internal structure in the MCG Operator. With this release, the print is fixed so that there are no collisions, thereby avoiding the repeated crashes of the MCG Operator.
 Story Points: ---
Clone Of: 2214288
: 2216402 (view as bug list) Environment:
Last Closed: 2023-08-02 16:07:42 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2214288    
Bug Blocks: 2216402    

Description Nimrod Becker 2023-06-21 07:39:20 UTC 
+++ This bug was initially created as a clone of Bug #2214288 +++

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

--- Additional comment from RHEL Program Management on 2023-06-12 13:32:38 UTC ---

This bug having no release flag set previously, is now set with release flag 'odf‑4.13.0' to '?', and so is being proposed to be fixed at the ODF 4.13.0 release. Note that the 3 Acks (pm_ack, devel_ack, qa_ack), if any previously set while release flag was missing, have now been reset since the Acks are to be set against a release flag.

--- Additional comment from Alexander Chuzhoy on 2023-06-12 13:53:02 UTC ---

the must-gather is here: https://file.rdu.redhat.com/~achuzhoy/bugs/2214288/
Comment 10 Tiffany Nguyen 2023-07-25 00:41:14 UTC 
Ran create and delete OBC tests about 4 hours and didn't see noobaa-operator pod restart.
Testing was done on 2 different clusters: ODF build 4.13.1-9 and 4.12.5-2.
Comment 15 errata-xmlrpc 2023-08-02 16:07:42 UTC 
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 (Moderate: Red Hat OpenShift Data Foundation 4.13.1 security and 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:4437
Comment 16 Nimrod Becker 2023-08-09 08:56:28 UTC 
*** Bug 2229863 has been marked as a duplicate of this bug. ***