Bug 1730212

Summary: mongod being killed by OOM killer
Product: Red Hat Satellite Reporter: Roman Plevka <rplevka>
Component: PulpAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED NOTABUG QA Contact: Bruno Rocha <rochacbruno>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.6.0CC: bkearney, dkliban, mmccune
Target Milestone: 6.6.0Keywords: Regression, Triaged
Target Release: Unused   
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: 2019-09-11 14:21:10 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 5 Roman Plevka 2019-07-30 15:09:13 UTC
sorry, the host got destroyed.

Comment 6 Mike McCune 2019-07-30 15:17:17 UTC
you can see from the test box that it is killing other processes too:

# grep "Out of memory" messages 

Jul 15 15:12:56 qe-testing-rhel7 kernel: Out of memory: Kill process 21308 (mongod) score 219 or sacrifice child
Jul 15 23:37:48 qe-testing-rhel7 kernel: Out of memory: Kill process 4598 (ruby) score 196 or sacrifice child
Jul 15 23:37:49 qe-testing-rhel7 kernel: Out of memory: Kill process 4601 (ruby-timer-thr) score 196 or sacrifice child
Jul 16 01:23:58 qe-testing-rhel7 kernel: Out of memory: Kill process 2004 (mongod) score 156 or sacrifice child


It just happens that Mongo is the largest consumer at the time but doesn't necessarily indicate any specific issue with Pulp, just that these tests are consuming more than the 20G of RAM available to the test VM.

Comment 9 Bryan Kearney 2019-09-11 14:21:10 UTC
Based on Comment 8, closing this out.