REVIEW: http://review.gluster.org/13676 (Tier: displaying status only one the nodes running tierd) posted (#1) for review on release-3.7 by hari gowtham (hari.gowtham005)
COMMIT: http://review.gluster.org/13676 committed in release-3.7 by Dan Lambright (dlambrig) ------ commit ef46724375bb83f59d165d61f45e5dc10e223699 Author: hari gowtham <hgowtham> Date: Tue Mar 8 17:22:35 2016 +0530 Tier: displaying status only one the nodes running tierd back-port of : http://review.gluster.org/#/c/13647/2 When tier status is given on a cluster where one node doesn't have tierd running, the status is shown as not started. The status of the node without tierd should not be displayed. This patch will skip if the current node if the status is not started >Change-Id: Ibeb39f13133f94a5869b020c5ccd9bd6992323f1 >BUG: 1315666 >Signed-off-by: hari gowtham <hgowtham> Change-Id: I15399db6bcdea68c0a7bebcf113329d37def6e1d BUG: 1316808 Signed-off-by: hari gowtham <hgowtham> Reviewed-on: http://review.gluster.org/13676 Smoke: Gluster Build System <jenkins.com> Tested-by: hari gowtham <hari.gowtham005> CentOS-regression: Gluster Build System <jenkins.com> NetBSD-regression: NetBSD Build System <jenkins.org> Reviewed-by: Dan Lambright <dlambrig>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.10, please open a new bug report. glusterfs-3.7.10 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] https://www.gluster.org/pipermail/gluster-users/2016-April/026164.html [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user
REVIEW: http://review.gluster.org/14229 (Tier/glusterd: Resetting the tier status value to not started) posted (#1) for review on release-3.7 by hari gowtham (hari.gowtham005)
COMMIT: http://review.gluster.org/14229 committed in release-3.7 by Atin Mukherjee (amukherj) ------ commit 09d4a110141394fab8fcc8498e498545e7d805bf Author: hari <hgowtham> 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> Change-Id: Ie4345bd7ce1d458574e36b70fe8994b3d758396a BUG: 1316808 Signed-off-by: hari <hgowtham> Reviewed-on: http://review.gluster.org/14229 Smoke: Gluster Build System <jenkins.com> Tested-by: hari gowtham <hari.gowtham005> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.com> Reviewed-by: Atin Mukherjee <amukherj>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.12, please open a new bug report. glusterfs-3.7.12 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] https://www.gluster.org/pipermail/gluster-devel/2016-June/049918.html [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user