Bug 1783587 - conmon should run in the pod slice
Summary: conmon should run in the pod slice
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Node
Version: 4.3.0
Hardware: Unspecified
OS: Linux
unspecified
high
Target Milestone: ---
: 4.3.0
Assignee: Ryan Phillips
QA Contact: Sunil Choudhary
URL:
Whiteboard:
Depends On: 1783585
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-12-13 23:22 UTC by Ryan Phillips
Modified: 2020-01-23 11:19 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1783585
Environment:
Last Closed: 2020-01-23 11:19:25 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift machine-config-operator pull 1344 0 None None None 2019-12-13 23:24:09 UTC
Red Hat Product Errata RHBA-2020:0062 0 None None None 2020-01-23 11:19:49 UTC

Description Ryan Phillips 2019-12-13 23:22:44 UTC
+++ This bug was initially created as a clone of Bug #1783585 +++

Description of problem:
conmon was moved to run under system.slice as a solution for it getting OOM killed. However, that could possibly lead to it taking away CPU cycles needed by system processes. Alternative solution that use a monitoring routine in CRI-O has been implemented to detect conmon getting OOM Killed.

Comment 4 errata-xmlrpc 2020-01-23 11:19:25 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:0062


Note You need to log in before you can comment on or make changes to this bug.