Description of problem: Failure reported at https://build.gluster.org/job/centos6-regression/7231/ More details at the gluster-devel thread: http://lists.gluster.org/pipermail/gluster-devel/2017-November/053920.html Version-Release number of selected component (if applicable): mainline How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
REVIEW: https://review.gluster.org/18683 (tests: fix spurious failure in bug-1345727-bricks-stop-on-no-quorum-validation.t) posted (#1) for review on master by Atin Mukherjee
COMMIT: https://review.gluster.org/18683 committed in master by ------------- tests: fix spurious failure in bug-1345727-bricks-stop-on-no-quorum-validation.t Add peer_count check before checking for brick status Change-Id: I0179ec29729ab6bbc3571eb6ffd631b7b0d15f7c BUG: 1510415 Signed-off-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-4.0.0, please open a new bug report. glusterfs-4.0.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/2018-March/000092.html [2] https://www.gluster.org/pipermail/gluster-users/