Description of problem: The command: gluster volume remove-brick <volname> linux-05:/gluster/brickx start fails silently if an invalid brick name is given. Version-Release number of selected component (if applicable): Version 3.4.2 How reproducible: Always Steps to Reproduce: 1. Execut command: gluster volume remove-brick <volname> linux-05:/gluster/<invalid_brick_name> start Actual results: No output Expected results: Command failed: invalid brick name Additional info:
GlusterFS 3.7.0 has been released (http://www.gluster.org/pipermail/gluster-users/2015-May/021901.html), and the Gluster project maintains N-2 supported releases. The last two releases before 3.7 are still maintained, at the moment these are 3.6 and 3.5. This bug has been filed against the 3,4 release, and will not get fixed in a 3.4 version any more. Please verify if newer versions are affected with the reported problem. If that is the case, update the bug with a note, and update the version if you can. In case updating the version is not possible, leave a comment in this bug report with the version you tested, and set the "Need additional information the selected bugs from" below the comment box to "bugs". If there is no response by the end of the month, this bug will get automatically closed.
GlusterFS 3.4.x has reached end-of-life.\ \ If this bug still exists in a later release please reopen this and change the version or open a new bug.