Description of problem: ------------------------ The error message seen on failure to start remove-brick on a volume is like this - Error while executing action: Cannot start remove Gluster Brick(s). One or more bricks are down. It needs to be corrected as follows - Error while executing action: Cannot start removing brick(s). One or more bricks are down. Version-Release number of selected component (if applicable): Red Hat Storage Console Version: 2.1.2-0.27.beta.el6_5 How reproducible: Always Steps to Reproduce: 1. On a distribute volume, kill one of the brick processes. 2. Wait till the brick status is reflected as down in the UI. 3. Select one of the bricks and click on Remove. ( The same can be tried with distributed-replicate volume with all the bricks in a replica set being killed ) Actual results: The above described message is seen. Expected results: The message needs to be corrected as explained above. Additional info:
The error messages for start/stop/commit remove bricks would be Cannot start removing Brick(s). No up server found in C1. Cannot stop removing Brick(s). No up server found in C1. Cannot commit removing Brick(s). No up server found in C1.
Verified as fixed in rhsc-3.0.0-0.7.master.el6_5. The message seen for failure to start remove-brick is as follows when a brick of a distribute volume is down, or when all bricks of a replica set are down in a distribute-replicate volume - Error while executing action: Cannot start removing Brick(s). One or more bricks are down. Marking as VERIFIED.
Hi Kanagaraj, Please review the edited text for technical accuracy and sign off.
Looks good to me.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2014-1277.html