Bug 1240955

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:	3.7.2	CC:	bugs, gluster-bugs, nsathyan, rhinduja, rjoseph, senaik, ssamanta, storage-qa-internal, surs, vagarwal
Target Milestone:	---	Keywords:	Triaged, ZStream
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:	USS
Fixed In Version:	glusterfs-3.7.3	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1240952	Environment:
Last Closed:	2015-07-30 09:49:42 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, 1240952
Bug Blocks:	1161015, 1162694, 1175735

Comment 1 Anand Avati 2015-07-08 08:56:32 UTC

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

Comment 2 Kaushal 2015-07-30 09:49:42 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.7.3, please open a new bug report.

glusterfs-3.7.3 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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/12078
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user