Bug 1799077

Summary: [vSphere/Baremetal] Nooba-operator keeps being OOM killed
Product: [Red Hat Storage] Red Hat OpenShift Container Storage Reporter: Pratik Surve <prsurve>
Component: Multi-Cloud Object GatewayAssignee: Romy Ayalon <rayalon>
Status: CLOSED ERRATA QA Contact: Pratik Surve <prsurve>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 4.3CC: assingh, ebenahar, etamir, jijoy, madam, nbecker, ocs-bugs, pbyregow, rayalon, tunguyen
Target Milestone: ---Keywords: AutomationBackLog, Regression
Target Release: OCS 4.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-14 09:45:55 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Comment 6 Romy Ayalon 2020-02-11 11:12:53 UTC 
As Nimrod said, The restart does not happen because of the PVC check, it's just a print when we check if there is a need for upgrade.
In general, a restart happens when a container in a pod dies.

More information would help us understand what is the reason for the restarts:
* description of the failing pod
* logs of the pod before the last restart (-- previous flag).
* Events - `oc get events --sort-by lastTimestamp`
Comment 15 Nimrod Becker 2020-02-25 15:20:24 UTC 
*** Bug 1806396 has been marked as a duplicate of this bug. ***
Comment 18 Nimrod Becker 2020-03-12 08:36:11 UTC 
*** Bug 1812634 has been marked as a duplicate of this bug. ***
Comment 20 Michael Adam 2020-03-13 09:42:51 UTC 
Patch is merged downstream.
https://ceph-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/OCS%20Build%20Pipeline%204.3/106/
has the patch.

CI is running.
Comment 21 Michael Adam 2020-03-13 16:42:57 UTC 
Build handed to QE as RC1
Comment 24 errata-xmlrpc 2020-04-14 09:45:55 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, 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/RHBA-2020:1437