Bug 1472372 - [3.4] Restart of atomic-openshift-node service terminates pod glusterfs mount
Summary: [3.4] Restart of atomic-openshift-node service terminates pod glusterfs mount
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Storage
Version: 3.4.1
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: 3.4.z
Assignee: Jan Safranek
QA Contact: Jianwei Hou
URL:
Whiteboard:
Depends On: 1423640 1424680
Blocks: 1462254 1466217 1472370
TreeView+ depends on / blocked
 
Reported: 2017-07-18 15:05 UTC by Scott Dodson
Modified: 2020-08-13 09:40 UTC (History)
25 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: When the atomic-openshift-node service got restarted, all processes in its control group are terminated, including the glusterfs mounted points. Consequence: Each glusterfs volume in OpenShift corresponds to one mounted point. If all mounting point are lost, so are all the volumes. Fix: Set the control group mode to terminate only the main process and leave the remaining glusterfs mounting points untouched. Result: When the atomic-openshift-node service is restarted no glusterfs mounting point is terminated.
Clone Of: 1423640
Environment:
Last Closed: 2017-10-25 13:02:19 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:3049 0 normal SHIPPED_LIVE OpenShift Container Platform 3.6, 3.5, and 3.4 bug fix and enhancement update 2017-10-25 15:57:15 UTC

Comment 1 Jan Safranek 2017-09-04 11:07:05 UTC 
Downstream PR: https://github.com/openshift/ose/pull/855
Comment 3 Jianwei Hou 2017-09-15 05:24:58 UTC 
This is still reproducible on v3.4.1.44.19, the package attached to the advisory has not fixed this bug.
Comment 4 Jan Safranek 2017-09-15 13:52:48 UTC 
It seems to be something wrong in our processes. This bug is fixed in enterprise-3.4 branch, however it is not part of tag v3.4.1.44.19. 

It will be part of the next release and it should be removed from errata RHBA-2017:30362-01.
Comment 5 Eric Paris 2017-09-26 17:44:59 UTC 
this PR broke the build.

http://download-node-02.eng.bos.redhat.com/brewroot/work/tasks/8264/14118264/build.log

kicking back to Jan. Brad is also looking.
Comment 6 Jan Safranek 2017-09-27 11:35:19 UTC 
Fixed by https://github.com/openshift/ose/pull/876
Comment 8 Jianwei Hou 2017-10-13 03:09:25 UTC 
Tested with 3.4.1.44.26-1.git.0.a62e88b.el7, verified this is fixed.
Comment 10 errata-xmlrpc 2017-10-25 13:02:19 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-2017:3049
Note You need to log in before you can comment on or make changes to this bug.