REVIEW: https://review.gluster.org/18600 (glusterd: delete source brick only once in reset-brick commit force) posted (#1) for review on release-3.10 by Atin Mukherjee
Problem Description: On a two node cluster, reset-brick commit force fails. Version: Mainline Reproducer steps: 1. Create a two node cluster. 2. Create a replica 2 volume, each brick hosted in different nodes gluster v create test-vol replica 2 172.17.0.2:/tmp/b1 172.17.0.3:/tmp/b1 force 3. gluster v reset-brick test-vol 172.17.0.2:/tmp/b1 start 4. gluster v reset-brick test-vol 172.17.0.2:/tmp/b1 172.17.0.2:/tmp/b1 commit force Step 4 fails. --- Additional comment from Atin Mukherjee on 2017-10-30 07:18:07 EDT --- upstream patch : --- Additional comment from Atin Mukherjee on 2017-10-30 07:20:20 EDT --- patch : https://review.gluster.org/#/c/18581 --- Additional comment from Worker Ant on 2017-10-31 07:14:53 EDT --- COMMIT: https://review.gluster.org/18581 committed in master by ------------- glusterd: delete source brick only once in reset-brick commit force While stopping the brick which is to be reset and replaced delete_brick flag was passed as true which resulted glusterd to free up to source brick before the actual operation. This results commit force to fail failing to find the source brickinfo. Change-Id: I1aa7508eff7cc9c9b5d6f5163f3bb92736d6df44 BUG: 1507466 Signed-off-by: Atin Mukherjee <amukherj>
COMMIT: https://review.gluster.org/18600 committed in release-3.10 by ------------- glusterd: delete source brick only once in reset-brick commit force While stopping the brick which is to be reset and replaced delete_brick flag was passed as true which resulted glusterd to free up to source brick before the actual operation. This results commit force to fail failing to find the source brickinfo. > mainline patch : https://review.gluster.org/#/c/18581/ Change-Id: I1aa7508eff7cc9c9b5d6f5163f3bb92736d6df44 BUG: 1507880 Signed-off-by: Atin Mukherjee <amukherj> (cherry picked from commit 0fb8acaa6ff80c43e46deac0ce66b29ae0df0ca4)
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.10.8, please open a new bug report. glusterfs-3.10.8 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/2017-December/000086.html [2] https://www.gluster.org/pipermail/gluster-users/