Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1512717 - Corrupt Sandbox Checkpoint Files
Corrupt Sandbox Checkpoint Files
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Pod (Show other bugs)
3.7.0
Unspecified Unspecified
high Severity high
: ---
: 3.7.z
Assigned To: Seth Jennings
DeShuai Ma
: OnlineStarter
Depends On: 1509799 1540606 1540608
Blocks:
  Show dependency treegraph
 
Reported: 2017-11-13 17:51 EST by Eric Paris
Modified: 2018-06-25 14:49 EDT (History)
22 users (show)

See Also:
Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Story Points: ---
Clone Of: 1509799
Environment:
Last Closed: 2018-04-05 05:30:40 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0636 None None None 2018-04-05 05:31 EDT

  None (edit)
Comment 2 Eric Paris 2017-11-13 18:13:02 EST
We saw a pod, with 44 of these completely break. It's like it just stopped making forward progress. I ran:

oc get --raw /debug/pprof/profile --server=https://172.31.71.195:10250 > profile

and it hung for about a hour. top showed 'openshift' using 100% CPU. I deleted the 'bad' sandboxes, restarted node, and now the node seems largely ok...
Comment 3 Seth Jennings 2017-11-13 18:13:34 EST
Upstream PR:
https://github.com/kubernetes/kubernetes/pull/55641
Comment 4 Seth Jennings 2017-11-14 10:10:23 EST
Origin PR:
https://github.com/openshift/origin/pull/17302
Comment 6 weiwei jiang 2018-01-25 02:26:28 EST
Checked with 
# openshift version 
openshift v3.7.26
kubernetes v1.7.6+a08f5eeb62
etcd 3.2.8

And can not reproduce this issue, so verify this.
Comment 10 errata-xmlrpc 2018-04-05 05:30:40 EDT
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:0636

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