Bug 1540912 - Kubelet crashes trying to free memory under MemoryPressure
Summary: Kubelet crashes trying to free memory under MemoryPressure
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Node
Version: 3.9.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 3.9.0
Assignee: Seth Jennings
QA Contact: DeShuai Ma
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-02-01 10:03 UTC by DeShuai Ma
Modified: 2018-03-28 14:25 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of:
Environment:
Last Closed: 2018-03-28 14:24:57 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0489 0 None None None 2018-03-28 14:25:20 UTC

Description DeShuai Ma 2018-02-01 10:03:38 UTC 
Description of problem:
Upstream issue: https://github.com/kubernetes/kubernetes/issues/58541
Upstream fix: https://github.com/kubernetes/kubernetes/pull/58574

Though I don't reproduce the bug, but it's better backport the fix to ocp3.9, just in case someone met it.

Version-Release number of selected component (if applicable):
openshift v3.9.0-0.34.0
kubernetes v1.9.1+a0ce1bc657
etcd 3.2.8

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Seth Jennings 2018-02-01 23:13:20 UTC 
Origin PR:
https://github.com/openshift/origin/pull/18403
Comment 3 DeShuai Ma 2018-02-05 08:55:26 UTC 
PR merged, verify the change.
Comment 6 errata-xmlrpc 2018-03-28 14:24:57 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-2018:0489
Note You need to log in before you can comment on or make changes to this bug.