Description of problem:
volume remove-brick commit: failed: use 'force' option as migration is in progress
not ok 20 , LINENUM:53
FAILED COMMAND: gluster --mode=script --wignore volume remove-brick patchy slave26.cloud.gluster.org:/d/backends/brick3 commit
ok 21, LINENUM:55
Version-Release number of selected component (if applicable):
Steps to Reproduce:
This is caused by a timing issue where the remove-brick commit is sent before the rebalance is complete. As the volume is empty and we don't care about the rebalance as part of this test, replace the remove-brick commit with remove-brick force.
REVIEW: https://review.gluster.org/18869 (tests: Spurious failure multiplex-limit-issue-151.t) posted (#1) for review on master by N Balachandran
COMMIT: https://review.gluster.org/18869 committed in master by \"N Balachandran\" <email@example.com> with a commit message- tests: Spurious failure multiplex-limit-issue-151.t
A timing issue caused the remove-brick commit to fail.
Replaced 'remove-brick commit' with 'remove-brick force'.
Signed-off-by: N Balachandran <firstname.lastname@example.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-4.0.0, please open a new bug report.
glusterfs-4.0.0 has been announced on the Gluster mailinglists , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.