+++ This bug was initially created as a clone of Bug #1517904 +++ Description of problem: https://build.gluster.org/job/regression-test-with-multiplex/543/consoleText 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): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: --- Additional comment from Nithya Balachandran on 2017-11-27 11:45:27 EST --- 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. --- Additional comment from Worker Ant on 2017-11-27 11:52:47 EST --- REVIEW: https://review.gluster.org/18869 (tests: Spurious failure multiplex-limit-issue-151.t) posted (#1) for review on master by N Balachandran --- Additional comment from Worker Ant on 2017-11-27 13:18:29 EST --- COMMIT: https://review.gluster.org/18869 committed in master by \"N Balachandran\" <nbalacha> 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'. Change-Id: I69144b2f7be34095dbd3a7d182e0bf01b27fb0a4 BUG: 1517904 Signed-off-by: N Balachandran <nbalacha>
REVIEW: https://review.gluster.org/19515 (tests: Spurious failure multiplex-limit-issue-151.t) posted (#1) for review on release-3.12 by N Balachandran
COMMIT: https://review.gluster.org/19515 committed in release-3.12 by "N Balachandran" <nbalacha> 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'. > Change-Id: I69144b2f7be34095dbd3a7d182e0bf01b27fb0a4 > BUG: 1517904 > Signed-off-by: N Balachandran <nbalacha> Change-Id: I69144b2f7be34095dbd3a7d182e0bf01b27fb0a4 BUG: 1542615 Signed-off-by: N Balachandran <nbalacha>
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.12.6, please open a new bug report. glusterfs-3.12.6 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/2018-February/033552.html [2] https://www.gluster.org/pipermail/gluster-users/