Description of problem: As $Summary Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
REVIEW: https://review.gluster.org/16746 (glusterd : log improvements in glusterd_op_stage_rebalance ()) posted (#1) for review on master by Atin Mukherjee (amukherj)
COMMIT: https://review.gluster.org/16746 committed in master by Atin Mukherjee (amukherj) ------ commit 7baa4bdf3a35f1957a37311477cf765fa4e85445 Author: Atin Mukherjee <amukherj> Date: Fri Feb 24 10:53:57 2017 +0530 glusterd : log improvements in glusterd_op_stage_rebalance () Include volume names in the respective staging failure error logs in rebalance staging Change-Id: Iaaab12a552930dd5274fbecec78f5735f883ab6b BUG: 1426509 Signed-off-by: Atin Mukherjee <amukherj> Reviewed-on: https://review.gluster.org/16746 Reviewed-by: Gaurav Yadav <gyadav> Smoke: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org>
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.11.0, please open a new bug report. glusterfs-3.11.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/announce/2017-May/000073.html [2] https://www.gluster.org/pipermail/gluster-users/