Description of problem: So far, kill_brick () waits a for a second after a brick is terminated. With brick multiplexing mode, given the detach operation of a brick is asynchronous this may not be sufficient. Instead, kill_brick () at the end should check for brick status to turn offline and then come out. 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/20635 (tests: kill_brick should wait for brick status to become offline) posted (#3) for review on master by Atin Mukherjee
COMMIT: https://review.gluster.org/20635 committed in master by "Atin Mukherjee" <amukherj> with a commit message- tests: kill_brick should wait for brick status to become offline Change-Id: I52e8eec7f334af37de433c444f4ddfc876fa56cc Fixes: bz#1614088 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-5.0, please open a new bug report. glusterfs-5.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] https://lists.gluster.org/pipermail/announce/2018-October/000115.html [2] https://www.gluster.org/pipermail/gluster-users/