[Bugs] [Bug 1175735] [USS]: snapd process is not killed once the glusterd comes back

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1175735



--- Comment #4 from Anand Avati <aavati at redhat.com> ---
COMMIT: http://review.gluster.org/9307 committed in release-3.6 by Raghavendra
Bhat (raghavendra at redhat.com) 
------
commit 9f0589646b4932b33ac0a913b1a23d8f279faf2b
Author: Sachin Pandit <spandit at redhat.com>
Date:   Wed Nov 5 11:09:59 2014 +0530

    USS : Kill snapd during glusterd restart if USS is disabled

    Problem : When glusterd is down on one of the nodes and during that
    time if USS is disabled then snapd will still be running
    in the node where glusterd was down.

    Solution : during restart of glusterd check if USS is disabled,
    if so then issue a kill for snapd.

    NOTE : The test case which I wrote in my previous patchset
    is facing some spurious failures, hence I thought of removing
    that test case. I'll add the test case once the issue is resolved.

    Change-Id: I2870ebb4b257d863cdfc319e8485b19e932576e9
    BUG: 1175735
    Signed-off-by: Sachin Pandit <spandit at redhat.com>
    Reviewed-on: http://review.gluster.org/9062
    Reviewed-by: Rajesh Joseph <rjoseph at redhat.com>
    Reviewed-by: Avra Sengupta <asengupt at redhat.com>
    Tested-by: Gluster Build System <jenkins at build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas at redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas at redhat.com>
    Signed-off-by: Sachin Pandit <spandit at redhat.com>
    Reviewed-on: http://review.gluster.org/9307
    Reviewed-by: Raghavendra Bhat <raghavendra at redhat.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.