Bug 1240952

Summary:	[USS]: snapd process is not killed once the glusterd comes back
Product:	[Community] GlusterFS	Reporter:	Avra Sengupta <asengupt>
Component:	snapshot	Assignee:	Avra Sengupta <asengupt>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	mainline	CC:	bugs, gluster-bugs, nsathyan, rhinduja, rjoseph, storage-qa-internal, surs, vagarwal
Target Milestone:	---	Keywords:	Reopened, Triaged, ZStream
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:	USS
Fixed In Version:	glusterfs-3.8rc2	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1240338
Clones:	1240955 (view as bug list)		Environment:
Last Closed:	2016-06-16 13:21:35 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:	1158883, 1240338
Bug Blocks:	1161015, 1162694, 1175735, 1240955

Comment 1 Anand Avati 2015-07-08 08:55:25 UTC

REVIEW: http://review.gluster.org/11575 (glusterd/snapd: Stop snapd daemon when glusterd is restarting) posted (#1) for review on master by Avra Sengupta (asengupt)

Comment 2 Anand Avati 2015-07-09 06:15:30 UTC

COMMIT: http://review.gluster.org/11575 committed in master by Rajesh Joseph (rjoseph) 
------
commit 34b3b00e5531c3992d913a65f60fe35f78b20f08
Author: Avra Sengupta <asengupt>
Date:   Wed Jul 8 14:18:19 2015 +0530

    glusterd/snapd: Stop snapd daemon when glusterd is restarting
    
    Stop snapd daemon when glusterd is coming back, if uss
    is disabled, or volume is stopped.
    
    Change-Id: I4313ecaff19de30f3e9ea76881994509402ed5b0
    BUG: 1240952
    Signed-off-by: Avra Sengupta <asengupt>
    Reviewed-on: http://review.gluster.org/11575
    Reviewed-by: Atin Mukherjee <amukherj>
    Tested-by: NetBSD Build System <jenkins.org>
    Reviewed-by: Rajesh Joseph <rjoseph>

Comment 3 Nagaprasad Sathyanarayana 2015-10-25 14:48:01 UTC

Fix for this BZ is already present in a GlusterFS release. You can find clone of this BZ, fixed in a GlusterFS release and closed. Hence closing this mainline BZ as well.

Comment 4 Niels de Vos 2016-06-16 13:21:35 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.8.0, please open a new bug report.

glusterfs-3.8.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://blog.gluster.org/2016/06/glusterfs-3-8-released/
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user