Bug 1245926

+++ This bug was initially created as a clone of Bug #1209123 +++

+++ This bug was initially created as a clone of Bug #1178100 +++

Description of problem:
=======================

gluster volume reset is used to "reset all the reconfigured options" and USS is one of them. But snapd process continues to be online 

[root@inception ~]# gluster v i vol_test | grep uss
features.uss: on
[root@inception ~]# ps -eaf | grep snapd
root      4182     1  0 15:10 ?        00:00:00 /usr/sbin/glusterfsd -s localhost --volfile-id snapd/vol_test -p /var/lib/glusterd/vols/vol_test/run/vol_test-snapd.pid -l /var/log/glusterfs/snaps/vol_test/snapd.log --brick-name snapd-vol_test -S /var/run/acfb4e617ee26303307f24cfb63c442e.socket --brick-port 49158 --xlator-option vol_test-server.listen-port=49158
root      4228  4111  0 15:10 pts/0    00:00:00 grep snapd
[root@inception ~]# gluster v reset vol_test
volume reset: success: reset volume successful
[root@inception ~]# gluster v i vol_test | grep uss
[root@inception ~]# ps -eaf | grep snapd
root      4182     1  0 15:10 ?        00:00:00 /usr/sbin/glusterfsd -s localhost --volfile-id snapd/vol_test -p /var/lib/glusterd/vols/vol_test/run/vol_test-snapd.pid -l /var/log/glusterfs/snaps/vol_test/snapd.log --brick-name snapd-vol_test -S /var/run/acfb4e617ee26303307f24cfb63c442e.socket --brick-port 49158 --xlator-option vol_test-server.listen-port=49158
root      4274  4111  0 15:11 pts/0    00:00:00 grep snapd
[root@inception ~]# 



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

glusterfs-3.6.0.40-1.el6rhs.x86_64


How reproducible:
================

always


Steps to Reproduce:
===================
1. Create 4 node cluster
2. Create and start a volume
3. Enable USS, confirm snapd process is started on all node
4. Check gluster v i vol-name, uss should be enabled
5. gluster v status should show snapshot-daemon online
6. Reset the volume using "gluster volume reset <vol-name>"
7. Check gluster v i vol-name, uss should not be listed
8. gluster v status should not show snapshot-daemon
9. check snapd process using "ps -eaf | grep snapd" on all nodes

Actual results:
===============
snapd process is online


Expected results:
=================
snapd process should not be running

--- Additional comment from RHEL Product and Program Management on 2015-01-02 05:23:36 EST ---

Since this issue was entered in bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

--- Additional comment from Nagaprasad Sathyanarayana on 2015-01-05 03:27:12 EST ---

As discussed and agreed by engineering leads & PM. deferring this BZ to next update.

--- Additional comment from Anand Avati on 2015-04-06 08:13:40 EDT ---

REVIEW: http://review.gluster.org/10138 (Snapshot:Stop snapd service during reset on a volume) posted (#1) for review on master by mohammed rafi  kc (rkavunga)

--- Additional comment from Anand Avati on 2015-04-06 08:16:35 EDT ---

REVIEW: http://review.gluster.org/10138 (Snapshot:Stop snapd service during reset on a volume) posted (#2) for review on master by mohammed rafi  kc (rkavunga)

--- Additional comment from Anand Avati on 2015-04-06 13:42:35 EDT ---

REVIEW: http://review.gluster.org/10138 (Snapshot:Stop snapd service during reset on a volume) posted (#3) for review on master by Niels de Vos (ndevos)

--- Additional comment from Anand Avati on 2015-04-07 02:12:59 EDT ---

REVIEW: http://review.gluster.org/10138 (Snapshot:Stop snapd service during reset on a volume) posted (#4) for review on master by mohammed rafi  kc (rkavunga)

--- Additional comment from Anand Avati on 2015-04-07 07:18:38 EDT ---

REVIEW: http://review.gluster.org/10138 (Snapshot:Stop snapd service during reset on a volume) posted (#5) for review on master by mohammed rafi  kc (rkavunga)