Red Hat Bugzilla – Bug 1020189
[RHSC] Commit button not enabled in the remove-bricks status dialog, even after the data migration has completed.
Last modified: 2015-05-13 12:27:15 EDT
Created attachment 813242 [details]
Description of problem:
After the data migration for a remove brick operation completes, the Commit button in the remove-brick status dialog does not get enabled. The Commit menu item in the drop-down menu beside the remove brick icon is however enabled once data migration completes.
Version-Release number of selected component (if applicable):
Red Hat Storage Console Version: 2.1.2-0.0.scratch.beta1.el6_4
Steps to Reproduce:
1. Create a volume and start it, mount it and create data on the mount point.
2. Start remove brick operation on the volume from the UI.
3. Once data migration is completed, check the status of remove brick from the UI.
Commit button is disabled.
Commit button should be enabled.
Find screenshot attached.
Lets fix this bug in the next build : CB5
Created attachment 815016 [details]
Seems like the bug,is due to some error from the gluster side.Because,when I tried to reproduce it,when the remove-brick was completed,I could see the commit button in the pop up enabled as can be seen in my attachment.Also to add to this,the remove brick status in the given attachment doesn't show the "completed" label indicating the possibility that status summary returned from the gluster may not be "FINISHED"(Button is enabled ONLY if status summary is "FINISHED").And also,this could be possible because,we can see the status for 3 other rows as unknown.So,this suggests that the bug may be in the aggregation of those results by gluster.
Verified as fixed in Red Hat Storage Console Version: 2.1.2-0.23.master.el6_5. Commit button in the status dialog now enabled after data migration gets completed.
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.