Bug 1031640

Summary: Gluster does not shut down w/ systemd
Product: [Fedora] Fedora Reporter: Bert DeKnuydt <Bert.Deknuydt>
Component: glusterfsAssignee: Kaleb KEITHLEY <kkeithle>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 19CC: barumuga, joe, jonathansteffan, kkeithle, ndevos, silas
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-11-18 13:04:27 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:

Description Bert DeKnuydt 2013-11-18 13:00:21 UTC
Description of problem:

Systemd command to stop gluster{d,fsd} does not work properly

Version-Release number of selected component (if applicable):

glusterfs-3.4.1-1.fc19.x86_64

How reproducible:

Always.

Steps to Reproduce:
0. Have a functional gluster environment.
1. As root: systemctl stop glusterd glusterfsd
   Give it some time to figure out.
2. As root: systemctl status glusterd glusterfsd
   See that it reports stopped.
3. As root: ps -ef|grep gluster
   See that the gluster stuff is still running. And
   even functional.

Actual results:

See above.

Expected results:

Nothing gluster alive anymore.

Additional info:

To unmount underlying fs, for example, explicit killing of the daemon's
is needed.

Comment 1 Niels de Vos 2013-11-18 13:04:27 UTC
(In reply to Bert DeKnuydt from comment #0)
> Expected results:
> 
> Nothing gluster alive anymore.

glusterd and glusterfsd should not stop the fuse-mounts. The mountpoint may well keep functioning even if there is no local glusterd/glusterfsd.

I think this is a duplicate of 1022542, please comment on that bug, it's proposed solution and give karma on the test-packages.

Thanks!

*** This bug has been marked as a duplicate of bug 1022542 ***