[Bugs] [Bug 1344634] fail delete volume operation if one of the glusterd instance is down in cluster

[bugzilla at redhat.com]

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



--- Comment #4 from Vijay Bellur <vbellur at redhat.com> ---
COMMIT: http://review.gluster.org/14692 committed in release-3.7 by Atin
Mukherjee (amukherj at redhat.com) 
------
commit 1a21cfba8e7a5f4ac1b8a8c3b8e06574b237420d
Author: Atin Mukherjee <amukherj at redhat.com>
Date:   Thu Jun 9 18:22:43 2016 +0530

    glusterd: fail volume delete if one of the node is down

    Backport of http://review.gluster.org/14681

    Deleting a volume on a cluster where one of the node in the cluster is down
is
    buggy since once that node comes back the resync of the same volume will
happen.
    Till we bring in the soft delete feature tracked in
    http://review.gluster.org/12963 this is a safe guard to block the volume
    deletion.

    Please note the test file which is backported from this commit has an issue
    where we start the volume and then try to delete it which is anyway going
to
    fail. So the test actually doesn't validate the fix.
    http://review.gluster.org/#/c/14693/ in master fixed the problem and the
same is
    ported as part of this commit as well.

    Change-Id: I9c13869c4a7e7a947f88842c6dc6f231c0eeda6c
    BUG: 1344634
    Signed-off-by: Atin Mukherjee <amukherj at redhat.com>
    Reviewed-on: http://review.gluster.org/14681
    Smoke: Gluster Build System <jenkins at build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.com>
    Reviewed-by: Kaushal M <kaushal at redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    Reviewed-on: http://review.gluster.org/14692
    Smoke: Gluster Build System <jenkins at build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai at redhat.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=RJ4aUSkKU9&a=cc_unsubscribe