Bug 1806396
| Summary: | [BAREMETAL] Noobaa-operator getting OOM Killed | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat OpenShift Container Storage | Reporter: | Pratik Surve <prsurve> |
| Component: | Multi-Cloud Object Gateway | Assignee: | Nimrod Becker <nbecker> |
| Status: | CLOSED DUPLICATE | QA Contact: | Raz Tamir <ratamir> |
| Severity: | high | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 4.3 | CC: | assingh, ebenahar, etamir, ocs-bugs, ratamir |
| Target Milestone: | --- | Keywords: | TechPreview |
| Target Release: | --- | ||
| 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-02-25 15:20:24 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 3
Yaniv Kaul
2020-02-24 07:21:41 UTC
Severity set to High as this is a tech prev platform 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!) The leak was identified and we (Romy) are now working on a fix. *** This bug has been marked as a duplicate of bug 1799077 *** |