Red Hat Bugzilla – Bug 1016494
Volume status operation after remove-brick is started on a volume fails, until remove-brick commit or remove-brick stop is done.
Last modified: 2015-10-07 08:15:59 EDT
Created attachment 809187 [details]
Description of problem:
After starting remove-brick on a volume, the gluster volume status command always fails with the following message -
[root@rhs ~]# gluster v status dis_rep_vol
Commit failed on localhost. Please check the log file for more details.
Once remove-brick commit, or remove-brick stop is performed, volume status works fine.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Start remove-brick on a volume.
2. Check volume status for that volume
Volume status command fails with above described message. After remove-brick is committed or stopped, volume status works.
Volume status command should display the status of the volume.
GlusterFS 3.7.0 has been released (http://www.gluster.org/pipermail/gluster-users/2015-May/021901.html), and the Gluster project maintains N-2 supported releases. The last two releases before 3.7 are still maintained, at the moment these are 3.6 and 3.5.
This bug has been filed against the 3,4 release, and will not get fixed in a 3.4 version any more. Please verify if newer versions are affected with the reported problem. If that is the case, update the bug with a note, and update the version if you can. In case updating the version is not possible, leave a comment in this bug report with the version you tested, and set the "Need additional information the selected bugs from" below the comment box to "email@example.com".
If there is no response by the end of the month, this bug will get automatically closed.
GlusterFS 3.4.x has reached end-of-life.
If this bug still exists in a later release please reopen this and change the version or open a new bug.