Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1513054 - Delete /var/lib/dockershim/sandbox/* after drain when upgrading from 3.6
Delete /var/lib/dockershim/sandbox/* after drain when upgrading from 3.6
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Upgrade (Show other bugs)
3.7.0
Unspecified Unspecified
high Severity urgent
: ---
: 3.7.0
Assigned To: Scott Dodson
liujia
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-11-14 11:32 EST by Eric Paris
Modified: 2018-02-05 15:12 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: No Doc Update
Doc Text:
no doctext
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-12-18 08:23:56 EST
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-2017:3464 normal SHIPPED_LIVE Red Hat OpenShift Container Platform 3.7 bug fix and enhancement update 2017-12-18 13:22:05 EST

  None (edit)
Description Eric Paris 2017-11-14 11:32:45 EST
We know that 3.6 is capable of creating bad files in /var/lib/dockershim/sandbox. After we drain a node in preparation to upgrade we should delete all of those files (on a well behaved system there would not be any such files after a drain).

A future 3.7.z version of openshift will correctly clean those files up themselves. However this is needed to clean up after 3.6 when running 3.7.4 (the GA version).
Comment 3 liujia 2017-11-15 05:25:56 EST
Verified on openshift-ansible-3.7.8-1.git.0.9a3db79.el7.noarch.

Monitor /var/lib/dockershim/sandbox/ directory during upgrade v3.6 to v3.7, the files in the directory will be cleaned up after drain node. And new files will be created when new pod created.
Comment 6 errata-xmlrpc 2017-12-18 08:23:56 EST
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-2017:3464

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