Bug 1806396 - [BAREMETAL] Noobaa-operator getting OOM Killed
Summary: [BAREMETAL] Noobaa-operator getting OOM Killed
Keywords:
Status: CLOSED DUPLICATE of bug 1799077
Alias: None
Product: Red Hat OpenShift Container Storage
Classification: Red Hat Storage
Component: Multi-Cloud Object Gateway
Version: 4.3
Hardware: Unspecified
OS: Unspecified
urgent
high
Target Milestone: ---
: ---
Assignee: Nimrod Becker
QA Contact: Raz Tamir
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-02-24 05:56 UTC by Pratik Surve
Modified: 2020-02-25 15:20 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-02-25 15:20:24 UTC
Embargoed:

Attachments (Terms of Use)

Comment 3 Yaniv Kaul 2020-02-24 07:21:41 UTC 
Severity?
Comment 4 Raz Tamir 2020-02-24 09:35:15 UTC 
Severity set to High as this is a tech prev platform
Comment 5 Yaniv Kaul 2020-02-25 11:47:59 UTC 
what did you see in the operator log when you've looked at it?
For example, didn't you find it strange it kept trying this:
time="2020-02-24T06:00:29Z" level=info msg="Not running in AWS. will attempt to create a ceph objectstore user" sys=openshift-storage/noobaa
time="2020-02-24T06:00:30Z" level=info msg="Not running in AWS. will attempt to create a ceph objectstore user" sys=openshift-storage/noobaa
time="2020-02-24T06:00:30Z" level=info msg="Not running in AWS. will attempt to create a ceph objectstore user" sys=openshift-storage/noobaa
time="2020-02-24T06:00:31Z" level=info msg="Not running in AWS. will attempt to create a ceph objectstore user" sys=openshift-storage/noobaa
time="2020-02-24T06:00:31Z" level=info msg="Not running in AWS. will attempt to create a ceph objectstore user" sys=openshift-storage/noobaa
time="2020-02-24T06:00:32Z" level=info msg="Not running in AWS. will attempt to create a ceph objectstore user" sys=openshift-storage/noobaa
time="2020-02-24T06:00:33Z" level=info msg="Not running in AWS. will attempt to create a ceph objectstore user" sys=openshift-storage/noobaa
time="2020-02-24T06:00:33Z" level=info msg="Not running in AWS. will attempt to create a ceph objectstore user" sys=openshift-storage/noobaa
time="2020-02-24T06:00:34Z" level=info msg="Not running in AWS. will attempt to create a ceph objectstore user" sys=openshift-storage/noobaa
time="2020-02-24T06:00:35Z" level=info msg="Not running in AWS. will attempt to create a ceph objectstore user" sys=openshift-storage/noobaa
time="2020-02-24T06:00:35Z" level=info msg="Not running in AWS. will attempt to create a ceph objectstore user" sys=openshift-storage/noobaa
[ykaul@ykaul glusterfs]$ grep -c "Not running"  ~/Downloads/noobaa-operator-846c8cc7d6-m4h7w.log 


So either the logic is wrong, or the log is flooded with this.

What else did you see there?
(Adding NEEDINFO on Raz, to ensure QE is looking at the logs!)
Comment 6 Nimrod Becker 2020-02-25 12:34:58 UTC 
The leak was identified and we (Romy) are now working on a fix.
Comment 7 Nimrod Becker 2020-02-25 15:20:24 UTC 

*** This bug has been marked as a duplicate of bug 1799077 ***
Note You need to log in before you can comment on or make changes to this bug.