Hide Forgot
Description of problem: After stopping remove brick from gluster cli, question mark icon appeared in the ui , but after a few seconds it changed to data migration and pending commit icon and clicking on commit removes the brick. Version-Release number of selected component (if applicable): rhsc-2.1.2-0.28.beta.el6_5.noarch How reproducible: Always Steps to Reproduce: 1. Create a distribute volume and start it. 2. Now start remove brick, wait till the data migration is completed. 3. stop remove brick from CLI by using the command "gluster vol remove-brick <volName> <brickPath> stop" Actual results: 1) '?' mark icon appeared in the UI. 2) After a few seconds, icon changed to remove-brick icon with pending commit. 3) Commiting the brick was sucessful. Expected results: 1) Icon should remain as question mark, only status should be enabled. Additional info:
Please find the sos reports here http://rhsqe-repo.lab.eng.blr.redhat.com/sosreports/rhsc/1044489
This seems to be an issue with GLUSTER. Tried the below commands from gluster CLI and it allows the commit even after stop is executed after remove brick. 1. 'gluster volume remove-brick <volname> <bricks> start' to start the remove brick operation. Waited for the completion of the same. 2. 'gluster volume remove-brick <volname> <bricks> status' shows the status as completed 3. 'gluster volume remove-brick <volname> <bricks> stop' stops the operation 4. 'gluster volume remove-brick <volname> <bricks> status' shows the status as completed 5. 'gluster volume remove-brick <volname> <bricks> commit' allowed and removes the brick permanently In Console, the status changes to COMPLETED with action pending because the command 'gluster volume remove-brick <volname> <bricks> status' returns a status as COMPLETED. And as the status is completed in UI commit & retain is enabled and it allows the action. Ideally in such a case GLUSTER should fail for commit if stop is already executed from CLI after completion of remove-brick.
We are not planning to fix it. Hence closing this BZ. If you think, it's applicable for 3.x release and would have an impact on customer, pls. open up a new BZ with the appropriate version. Thanks, -Dusmant