Bug 1472372
| Summary: | [3.4] Restart of atomic-openshift-node service terminates pod glusterfs mount | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Scott Dodson <sdodson> |
| Component: | Storage | Assignee: | Jan Safranek <jsafrane> |
| Status: | CLOSED ERRATA | QA Contact: | Jianwei Hou <jhou> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.4.1 | CC: | aos-bugs, aos-storage-staff, atumball, bchilds, bleanhar, bmchugh, csaba, ekuric, eparis, erich, hchiramm, jchaloup, jialiu, jkaur, jnordell, jokerman, jsafrane, knakayam, mmccomas, mrobson, rcyriac, rhs-bugs, sdodson, tlarsson, trankin |
| Target Milestone: | --- | Keywords: | NeedsTestCase, Reopened |
| Target Release: | 3.4.z | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| 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.
|
Story Points: | --- |
| Clone Of: | 1423640 | Environment: | |
| Last Closed: | 2017-10-25 13:02:19 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1423640, 1424680 | ||
| Bug Blocks: | 1462254, 1466217, 1472370 | ||
|
Comment 1
Jan Safranek
2017-09-04 11:07:05 UTC
This is still reproducible on v3.4.1.44.19, the package attached to the advisory has not fixed this bug. 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. 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. Tested with 3.4.1.44.26-1.git.0.a62e88b.el7, verified this is fixed. 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 |