[Bugs] [Bug 1316808] Data Tiering:tier volume status shows as in-progress on all nodes of a cluster even if the node is not part of volume

[bugzilla at redhat.com]

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



--- Comment #5 from Vijay Bellur <vbellur at redhat.com> ---
COMMIT: http://review.gluster.org/14229 committed in release-3.7 by Atin
Mukherjee (amukherj at redhat.com) 
------
commit 09d4a110141394fab8fcc8498e498545e7d805bf
Author: hari <hgowtham at redhat.com>
Date:   Thu Apr 28 19:36:25 2016 +0530

    Tier/glusterd: Resetting the tier status value to not started

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

    Problem: during a volume restart or tier start force, the
    value of tier status is set as started irrespective of the result.

    Fix: The appropriate value of status is set during the restart of
    rebalance function.

    >Change-Id: I6164f0add48542a57dee059e80fa0f9bb036dbef
    >BUG: 1315666
    >Signed-off-by: hari <hgowtham at redhat.com>

    Change-Id: Ie4345bd7ce1d458574e36b70fe8994b3d758396a
    BUG: 1316808
    Signed-off-by: hari <hgowtham at redhat.com>
    Reviewed-on: http://review.gluster.org/14229
    Smoke: Gluster Build System <jenkins at build.gluster.com>
    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.com>
    Reviewed-by: Atin Mukherjee <amukherj 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.