Red Hat Bugzilla – Bug 765470
Add-brick gives confusing error message when it fails during replace-brick.
Last modified: 2015-11-03 18:03:51 EST
[root@RHEL6 ~]# gluster volume replace-brick doa 10.1.11.116:/export/sda/exports/exp2 10.1.11.116:/export/sda/exports/exp1 start
replace-brick started successfully
[root@RHEL6 exp1]# gluster volume info
Volume Name: doa
Number of Bricks: 2 x 2 = 4
[root@RHEL6 exp1]# gluster volume add-brick doa 10.1.11.115:/export/sda/exports/exp4 10.1.11.116:/export/sda/exports/exp4
Volume doa: replace brick is running and the brick 10.1.11.116:/export/sda/exports/exp4 you are trying to add is the destination brick for replace brick
Even though the bricks involved in add-brick are neither part of volume nor replace-brick , it gives above error message.
CHANGE: http://review.gluster.com/631 (add-brick, stop-volume, remove-brick are the operations that are explicitly) merged in release-3.2 by Vijay Bellur (email@example.com)
[root@RHEL6 ~]# gluster volume create doa stripe 2 10.1.11.115:/export/sda/exports/exp1 10.1.11.116:/export/sda/exports/exp1 10.1.11.115:/export/sda/exports/exp2 10.1.11.116:/export/sda/exports/exp2
Creation of volume doa has been successful. Please start the volume to access data.
[root@RHEL6 ~]# gluster volume start doa Starting volume doa has been successful
[root@RHEL6 ~]# gluster volume replace-brick doa 10.1.11.116:/export/sda/exports/exp2 10.1.11.115:/export/sda/exports/exp3 start replace-brick started successfully
[root@RHEL6 ~]# gluster volume add-brick doa 10.1.11.115:/export/sda/exports/exp5 10.1.11.115:/export/sda/exports/exp4
Replace brick is in progress on volume doa. Please try after replace-brick operation is committed or aborted.
It gives appropriate error message now.
Reopening the bug
upon executing the above said said steps replace-brick says "Replace-brick failed to start" and does not give appropriate message
@shylesh, "replace-brick failed to start" is not an inappropriate message, though I agree that it doesn't give the reason why it failed.
This bug is tracking an issue with an error message which was supplying the user with an incorrect message regarding the cause of failure of replace-brick. You should open a new bug to track inadequate error messages. This bug should be reopened only to fix an incomplete fix/patch for the original problem.
Let me know your comments, and if you agree with me, please close this bug and open a different one for the problem you see.
@kp, The fix is not yet in for master so reopened, will close once the patch is in for the master.
CHANGE: http://review.gluster.com/2740 (glusterd: Fail volume 'modify' operations when rb is ongoing) merged in master by Vijay Bellur (firstname.lastname@example.org)
*** Bug 763765 has been marked as a duplicate of this bug. ***
Now proper error messages will be shown.