Red Hat Bugzilla – Bug 867700
GUI removes brick from a volume when volume is in stopped state, without displaying message that says "volume needs to be started"
Last modified: 2013-07-03 02:06:42 EDT
Description of problem:
When trying to remove a brick from a gluster volume through the gluster CLI, when the volume is in 'stopped' state, using the command -
gluster volume remove-brick <vol-name> <brick> start
the following message is seen -
"Volume <vol-name> needs to be started before remove-brick (you can use 'force' or 'commit' to override this behavior)"
When trying to remove a brick from the GUI when the volume is in the 'stopped' state, the operation succeeds without a similar message.
Version-Release number of selected component (if applicable):
Red Hat Storage Console Version: 2.0.techpreview1-3.el6rhs
Steps to Reproduce:
1.Create a gluster volume from the GUI.
2.Select the created volume and click on the sub-tab 'Bricks'.
3.Select the bricks to be removed and click on 'Remove Bricks'.
4.When asked for confirmation, click on 'yes'.
The brick that was selected for removal was successfully removed without displaying any message saying the volume needs to be started.
An appropriate message, like the one displayed by the CLI should be displayed.
remove-brick with 'start' option is an asynchronous task, which is currently not supported by the console. We use the synchronous mode using the 'force' option by default.
Work to support asynchronous tasks is in progress, and is tracked through https://bugzilla.redhat.com/show_bug.cgi?id=850422
When we start supporting async tasks, it will include remove-brick as well.
So I'm closing this bug.