Bug 1071411 - gluster cli : Incorrect grammar in the "Usage" of "rebalance" command
Summary: gluster cli : Incorrect grammar in the "Usage" of "rebalance" command
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: cli
Version: pre-release
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: Susant Kumar Palai
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On: 1062564
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-28 17:26 UTC by Susant Kumar Palai
Modified: 2014-11-11 08:28 UTC (History)
7 users (show)

Fixed In Version: glusterfs-3.6.0beta1
Clone Of: 1062564
Environment:
Last Closed: 2014-11-11 08:28:23 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Comment 1 Anand Avati 2014-02-28 17:32:17 UTC 
REVIEW: http://review.gluster.org/7172 (cli:  Rectify grammar in the "Usage" of "rebalance" command) posted (#1) for review on master by susant palai (spalai)
Comment 2 Anand Avati 2014-03-02 03:01:38 UTC 
COMMIT: http://review.gluster.org/7172 committed in master by Anand Avati (avati) 
------
commit ee150bd45e4976bc31d1660102d487982b0ce83d
Author: Susant Palai <spalai>
Date:   Fri Feb 28 17:19:43 2014 +0000

    cli:  Rectify grammar in the "Usage" of "rebalance" command
    
    Problem: Currently Usage of rebalance command is : " Usage: volume rebalance
    <VOLNAME> [fix-layout] {start|stop|status} [force] "
    
    1) "force" option can be only used with "start" .
    
    2) "fix-layout" option can be only used with "start"
    
    But the current usage says "fix-layout" operation can be stopped and can get the
    status of "fix-layout" operation and also "stop" ,"status" operation can be used
    with "force" option which is not correct.
    
    Change-Id: I48e6c64c124f5803c8f09c78df0e14dc2b6a348a
    BUG: 1071411
    Signed-off-by: Susant Palai <spalai>
    Reviewed-on: http://review.gluster.org/7172
    Reviewed-by: Anand Avati <avati>
    Tested-by: Anand Avati <avati>
Comment 3 Niels de Vos 2014-09-22 12:36:29 UTC 
A beta release for GlusterFS 3.6.0 has been released. Please verify if the release solves this bug report for you. In case the glusterfs-3.6.0beta1 release does not have a resolution for this issue, leave a comment in this bug and move the status to ASSIGNED. If this release fixes the problem for you, leave a note and change the status to VERIFIED.

Packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update (possibly an "updates-testing" repository) infrastructure for your distribution.

[1] http://supercolony.gluster.org/pipermail/gluster-users/2014-September/018836.html
[2] http://supercolony.gluster.org/pipermail/gluster-users/
Comment 4 Niels de Vos 2014-11-11 08:28:23 UTC 
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.6.1, please reopen this bug report.

glusterfs-3.6.1 has been announced [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://supercolony.gluster.org/pipermail/gluster-users/2014-November/019410.html
[2] http://supercolony.gluster.org/mailman/listinfo/gluster-users
Note You need to log in before you can comment on or make changes to this bug.