Description of problem: The icon shown in the activities column of the volume after stop rebalance should reflect the actual status of the activity and should be in sync with the gluster CLI output. Sometimes, even if the rebalance was completed when stop was fired, the activities column shows as stopped whereas if the status is invoked it shows correctly as completed in the status dialog. The activities column should reflect the correct status of the activity. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Go to Volumes tab and select a volume from the list 2. Start rebalance by clicking the "Rebalance" menu option 3. Wait for sometime and click the "Stop" from drop down menu option in activities column Actual results: The activities column icon changes to stopped whereas the activities got finished by the time stop was fired. Expected results: If the activity got finished by the time stop was fired, the same should be reflected in volume activities column as well. Additional info:
The above happens when glusterd is made down and rebalance is started, wait for some time and click on rebalance stop it actually stops rebalance and tasks pane shows that task is aborted.
The above happens when glusterd is made down and rebalance is started, wait for some time and click on rebalance stop it actually stops rebalance and tasks pane shows that task is aborted. In the above scenario it gives the error attached in the "stoprebalance". This can be verified only when the following BZ : 1015045 is fixed.
Created attachment 823945 [details] Attaching stop rebalance error dialog.
verified and works fine in cb11 rhsc-2.1.2-0.27.beta.el6_5.noarch. When rebalance completes on all the nodes and clicked on stop button, it updates the icon as completed. when glusterd is made down and clicked on stop button, it updates the icon as failed.
Doc Text is not required as its a new feature and we already have an RFE
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-0208.html