Description of problem: While testing http://review.gluster.org/#/c/14347 I figured out that on a multi node cluster, if rebalance start is triggered with one of the glusterd instance been down which hosts one of the bricks, the failure message doesn't show the hostname. root@54deb20dc641:/home/glusterfs# gluster v rebalance test-vol start volume rebalance: test-vol: failed: Host node of brick /tmp/b1 is down Also the message says that brick is down but glusterd is not. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Create a multi node cluster 2. Create volume spanning over multiple nodes, start it 3. Trigger rebalance Actual results: Error message is misleading Expected results: Error message should be correct. Additional info:
REVIEW: http://review.gluster.org/14495 (Glusterd: printing the node on error message of rebalance) posted (#1) for review on master by hari gowtham (hari.gowtham005)
REVIEW: http://review.gluster.org/14495 (Glusterd: printing the node details on error message of rebalance) posted (#2) for review on master by hari gowtham (hari.gowtham005)
REVIEW: http://review.gluster.org/14495 (Glusterd: printing the node details on error message of rebalance) posted (#3) for review on master by hari gowtham (hari.gowtham005)
REVIEW: http://review.gluster.org/14495 (Glusterd: printing the node details on error message of rebalance) posted (#4) for review on master by hari gowtham (hari.gowtham005)
COMMIT: http://review.gluster.org/14495 committed in master by Atin Mukherjee (amukherj) ------ commit fb57ac1acb228301edb98f2fe7cf93471363eb4a Author: hari <hgowtham> Date: Mon May 23 12:07:21 2016 +0530 Glusterd: printing the node details on error message of rebalance Problem: on the rebalance start with one of the glusterd being down among the volume, the error message says only about the brick path. Fix: adding the node details Change-Id: I5827d3a9a15b0461c9ce3a51c0b16246ca58f335 BUG: 1337899 Signed-off-by: hari <hgowtham> Reviewed-on: http://review.gluster.org/14495 Tested-by: hari gowtham <hari.gowtham005> Smoke: Gluster Build System <jenkins.com> 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.9.0, please open a new bug report. glusterfs-3.9.0 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] http://lists.gluster.org/pipermail/gluster-users/2016-November/029281.html [2] https://www.gluster.org/pipermail/gluster-users/