[Bugs] [Bug 1347509] 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
bugzilla at redhat.com
Mon Jun 20 04:09:10 UTC 2016
https://bugzilla.redhat.com/show_bug.cgi?id=1347509
--- Comment #2 from Vijay Bellur <vbellur at redhat.com> ---
COMMIT: http://review.gluster.org/14749 committed in release-3.8 by Atin
Mukherjee (amukherj at redhat.com)
------
commit 362f90b5612c0f38894684d1d6f3bd66a31fe5b1
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/
back-port of : http://review.gluster.org/#/c/14229/
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>
Change-Id: I8e8e0662535c9dbe09eb6c7078422b40c218b473
BUG: 1347509
Signed-off-by: hari gowtham <hgowtham at redhat.com>
Reviewed-on: http://review.gluster.org/14749
Tested-by: hari gowtham <hari.gowtham005 at gmail.com>
Reviewed-by: Atin Mukherjee <amukherj at redhat.com>
Smoke: Gluster Build System <jenkins at build.gluster.org>
NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
--
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