[Bugs] [Bug 1375565] Detach tier commit is allowed when detach tier start goes into failed state

bugzilla at redhat.com bugzilla at redhat.com
Fri Sep 16 12:56:56 UTC 2016


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



--- Comment #4 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: http://review.gluster.org/15492 committed in release-3.8 by Dan
Lambright (dlambrig at redhat.com) 
------
commit 7f4a693ee55d9c517f6b583e551518a6d643e6ff
Author: hari gowtham <hgowtham at redhat.com>
Date:   Fri Sep 9 12:26:52 2016 +0530

    Tier: failing detach commit on detach failure and in-progress

            back-port of:http://review.gluster.org/#/c/15438/

    PROBLEM: if detach status has failed or if it remains in progress
    we allow detach commit to happen. only detach force should
    be allowed.

    FIX: check the detach status for failure or inprogress and disallow
    with the apt error message.

    > Change-Id: Ib97d540fec67717bb55c18d133187c665cf69ef1
    > BUG: 1374584
    > Signed-off-by: hari gowtham <hgowtham at redhat.com>
    > Reviewed-on: http://review.gluster.org/15438
    > Smoke: Gluster Build System <jenkins at build.gluster.org>
    > Tested-by: hari gowtham <hari.gowtham005 at gmail.com>
    > NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    > CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
    > Reviewed-by: Dan Lambright <dlambrig at redhat.com>
    > Tested-by: Dan Lambright <dlambrig at redhat.com>

    Change-Id: I4098c45f5338f8bc4262e75fa6630dabc755e133
    BUG: 1375565
    Signed-off-by: hari gowtham <hgowtham at redhat.com>
    Reviewed-on: http://review.gluster.org/15492
    Tested-by: hari gowtham <hari.gowtham005 at gmail.com>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
    Smoke: Gluster Build System <jenkins at build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    Reviewed-by: Dan Lambright <dlambrig at redhat.com>

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


More information about the Bugs mailing list