Currently 'gluster volume status all --xml' output doesn't have brick parameters. We are expecting 1. replace-brick task containing sourceBrick and destBrick 2. remove-brick task containing removal brick(s) These parameters are needed to get actual task progress by running 'gluster volume remove-brick/replace-brick status'
REVIEW: http://review.gluster.org/5771 (cli,glusterd: Task parameters in xml output) posted (#1) for review on master by Kaushal M (kaushal)
REVIEW: http://review.gluster.org/5771 (cli,glusterd: Task parameters in xml output) posted (#2) for review on master by Kaushal M (kaushal)
REVIEW: http://review.gluster.org/5771 (cli,glusterd: Task parameters in xml output) posted (#3) for review on master by Kaushal M (kaushal)
REVIEW: http://review.gluster.org/5771 (cli,glusterd: Task parameters in xml output) posted (#4) for review on master by Kaushal M (kaushal)
REVIEW: http://review.gluster.org/5771 (cli,glusterd: Task parameters in xml output) posted (#5) for review on master by Kaushal M (kaushal)
COMMIT: http://review.gluster.org/5771 committed in master by Vijay Bellur (vbellur) ------ commit 91cd0eae2cc1d96cbafa6457835f146503355238 Author: Kaushal M <kaushal> Date: Wed Sep 4 11:50:40 2013 +0530 cli,glusterd: Task parameters in xml output This patch introduces task parameters for the asynchronus task shown in volume status. The parameters are only given for xml output. The parameters shown currently are, - source and destination bricks for replace-brick tasks ...... <tasks> <task> <type>Replace brick</type> <id>3d1a1005-9d2e-4ae0-bd62-577bc1d333a3</id> <status>1</status> <params> <srcBrick>archm:/export/test4</srcBrick> <dstBrick>archm:/export/test-replace1</dstBrick> </params> </task> </tasks> ...... - list of bricks being removed for remove-brick tasks ...... <tasks> <task> <type>Remove brick</type> <id>901c20ca-0da2-41de-8669-5f0caca6b846</id> <status>1</status> <params> <brick>archm:/export/test2</brick> <brick>archm:/export/test3</brick> </params> </task> </tasks> ...... The changes for non-xml output will be done in a subsequent patch. Change-Id: I322afe2f83ed8adeddb99f7962c25911204dc204 BUG: 916577 Signed-off-by: Kaushal M <kaushal> Reviewed-on: http://review.gluster.org/5771 Reviewed-by: Vijay Bellur <vbellur> Tested-by: Vijay Bellur <vbellur>
REVIEW: http://review.gluster.org/5973 (cli,glusterd: Task parameters in xml output) posted (#1) for review on release-3.4 by Kaushal M (kaushal)
COMMIT: http://review.gluster.org/5973 committed in release-3.4 by Anand Avati (avati) ------ commit 999c177ffba9b940d977901ede3aaf55c236e255 Author: Kaushal M <kaushal> Date: Wed Sep 4 11:50:40 2013 +0530 cli,glusterd: Task parameters in xml output Backport of 91cd0eae2cc1d96cbafa6457835f146503355238 from master This patch introduces task parameters for the asynchronus task shown in volume status. The parameters are only given for xml output. The parameters shown currently are, - source and destination bricks for replace-brick tasks ...... <tasks> <task> <type>Replace brick</type> <id>3d1a1005-9d2e-4ae0-bd62-577bc1d333a3</id> <status>1</status> <params> <srcBrick>archm:/export/test4</srcBrick> <dstBrick>archm:/export/test-replace1</dstBrick> </params> </task> </tasks> ...... - list of bricks being removed for remove-brick tasks ...... <tasks> <task> <type>Remove brick</type> <id>901c20ca-0da2-41de-8669-5f0caca6b846</id> <status>1</status> <params> <brick>archm:/export/test2</brick> <brick>archm:/export/test3</brick> </params> </task> </tasks> ...... The changes for non-xml output will be done in a subsequent patch. BUG: 916577 Change-Id: Iade8a4974aefc5ffb080553496ae5a3169055090 Signed-off-by: Kaushal M <kaushal> Reviewed-on: http://review.gluster.org/5973 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Anand Avati <avati>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.4.3, please reopen this bug report. glusterfs-3.4.3 has been announced on the Gluster Developers mailinglist [1], packages for several distributions should already be or become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. The fix for this bug likely to be included in all future GlusterFS releases i.e. release > 3.4.3. In the same line the recent release i.e. glusterfs-3.5.0 [3] likely to have the fix. You can verify this by reading the comments in this bug report and checking for comments mentioning "committed in release-3.5". [1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/5978 [2] http://news.gmane.org/gmane.comp.file-systems.gluster.user [3] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/6137