Description of problem: Few instances of the failures: https://build.gluster.org/job/regression-test-burn-in/1447/consoleFull https://build.gluster.org/job/regression-test-burn-in/1435/consoleFull Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
REVIEW: http://review.gluster.org/15085 (tests: fix spurious failure in tests/bugs/glusterd/bug-1089668.t) posted (#1) for review on master by Atin Mukherjee (amukherj)
COMMIT: http://review.gluster.org/15085 committed in master by Jeff Darcy (jdarcy) ------ commit 2650f8b1101a1f345f310475841569feb852bf4b Author: Atin Mukherjee <amukherj> Date: Thu Aug 4 11:51:27 2016 +0530 tests: fix spurious failure in tests/bugs/glusterd/bug-1089668.t Instead of rebalance stop, its always better to wait for rebalance to complete as the former doesn't have any purpose. Change-Id: Ia1bc2a34d937a0a96543bebd257dcda619f12474 BUG: 1363948 Signed-off-by: Atin Mukherjee <amukherj> Reviewed-on: http://review.gluster.org/15085 Smoke: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: Jeff Darcy <jdarcy>
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/