Bug 1240952 - [USS]: snapd process is not killed once the glusterd comes back
Summary: [USS]: snapd process is not killed once the glusterd comes back
Alias: None
Product: GlusterFS
Classification: Community
Component: snapshot
Version: mainline
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Avra Sengupta
QA Contact:
Whiteboard: USS
Depends On: 1158883 1240338
Blocks: 1161015 1162694 1175735 1240955
TreeView+ depends on / blocked
Reported: 2015-07-08 08:38 UTC by Avra Sengupta
Modified: 2016-06-16 13:21 UTC (History)
8 users (show)

Fixed In Version: glusterfs-3.8rc2
Doc Type: Bug Fix
Doc Text:
Clone Of: 1240338
: 1240955 (view as bug list)
Last Closed: 2016-06-16 13:21:35 UTC
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:

Attachments (Terms of Use)

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@redhat.com)

Comment 2 Anand Avati 2015-07-09 06:15:30 UTC
COMMIT: http://review.gluster.org/11575 committed in master by Rajesh Joseph (rjoseph@redhat.com) 
commit 34b3b00e5531c3992d913a65f60fe35f78b20f08
Author: Avra Sengupta <asengupt@redhat.com>
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@redhat.com>
    Reviewed-on: http://review.gluster.org/11575
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>

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

Note You need to log in before you can comment on or make changes to this bug.