Bug 1294733

Summary: Unable to reboot atomic host after stopping RHGS container
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Shruti Sampat <ssampat>
Component: rhgs-server-containerAssignee: Mohamed Ashiq <mliyazud>
Status: CLOSED CURRENTRELEASE QA Contact: Shruti Sampat <ssampat>
Severity: low Docs Contact:
Priority: unspecified    
Version: rhgs-3.1CC: hchiramm, mliyazud, pprakash, rcyriac, sankarshan, ssampat
Target Milestone: ---Keywords: ZStream
Target Release: RHGS 3.1.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: RHELAH 7.2.2, rhgs-server-docker-3.1.2-7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-03 10:50:33 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: 1294459    
Bug Blocks:    
Attachments:
Description Flags
screenshot none

Description Shruti Sampat 2015-12-30 04:18:13 UTC 
Created attachment 1110437 [details]
screenshot

Description of problem:
-----------------------

Trying to reboot an atomic host after stopping a running RHGS container has problems due to failure in unmounting /var and /usr. See screenshot attached.

Version-Release number of selected component (if applicable):
-------------------------------------------------------------
rhgs-server-rhel7:3.1.2-3

How reproducible:
-----------------
Frequently

Steps to Reproduce:
-------------------
1. Stop a running RHGS container on atomic host. Doing this is impacted by BZ#1293667 every single time, but restarting docker service seems to solve the problem.
2. Remove the stopped container using `docker rm'.
3. Reboot the atomic host.

Actual results:
---------------
The machine does not come up for a few hours and stays in the state seen in the screenshot. After a couple of hours it comes up.

Expected results:
-----------------
Rebooting the machine should be smooth.
Comment 2 Humble Chirammal 2016-01-02 05:11:28 UTC 
I believe the reboot delay comes only when there was no 'graceful shutdown' (docker stop)  of the container and we fail to do it ( #docker stop ) when the volumes are not mounted inside the container. In short, this is a side effect of 'unsuccessful bind mount' issue which is mentioned @ bz#1293669. Can you please confirm this thought ?  If that is the case, it is almost tangent to an expected result.
Comment 6 Shruti Sampat 2016-01-27 10:22:49 UTC 
Issue is still reproducible with steps mentioned in comment #0. Re-assigning BZ.
Comment 9 Shruti Sampat 2016-02-17 09:37:00 UTC 
Verified as fixed in rhgs-server-docker-3.1.2-7 with latest RHEL 7.2 atomic host.