Description of problem: cli getspec asks volid instead of volname Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: Execute "gluster system getspec" Actual results: Usage: system:: getspec <VOLID> Expected results: Usage: system:: getspec <VOLNAME> Additional info:
REVIEW: http://review.gluster.org/8342 (cli : glusterd getspec usage correction) posted (#1) for review on master by Atin Mukherjee (amukherj)
REVIEW: http://review.gluster.org/8342 (cli : glusterd getspec usage correction) posted (#2) for review on master by Krishnan Parthasarathi (kparthas)
REVIEW: http://review.gluster.org/8342 (cli : glusterd getspec usage correction) posted (#3) for review on master by Atin Mukherjee (amukherj)
COMMIT: http://review.gluster.org/8342 committed in master by Krishnan Parthasarathi (kparthas) ------ commit 7d74792d225196585c24f8843bdba61a14c1c3d3 Author: Atin Mukherjee <amukherj> Date: Tue Jul 22 11:43:09 2014 +0530 cli : glusterd getspec usage correction gluster system getspec asks to input volume-id instead of volume name Change-Id: I0baef9c937fc8948477aa65c8f98916b28c1e484 BUG: 1121870 Signed-off-by: Atin Mukherjee <amukherj> Reviewed-on: http://review.gluster.org/8342 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Krishnan Parthasarathi <kparthas> Tested-by: Krishnan Parthasarathi <kparthas>
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.7.0, please open a new bug report. glusterfs-3.7.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user