Bug 1309123

Summary: rebalance help text does not match command parser
Product: [Community] GlusterFS Reporter: Joe Julian <joe>
Component: cliAssignee: hari gowtham <hgowtham>
Status: CLOSED EOL QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: 3.7.7CC: amukherj, bugs, hgowtham
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-03-08 10:50:48 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Joe Julian 2016-02-16 22:49:57 UTC
Breaking from the model of using the help text as the model for the command parser, rebalance for tiers doesn't display the complete help text for "gluster volume help":

volume rebalance <VOLNAME> {{fix-layout start} | {start [force]|stop|status}} - rebalance operations

This is missing the tier options, at minimum.

volume rebalance <VOLNAME> {{fix-layout start} | [tier] {start [force]|stop|status}} - rebalance operations

Comment 1 Atin Mukherjee 2017-01-23 05:14:17 UTC
Can this be fixed as part of 3.10 Hari?

Comment 2 hari gowtham 2017-01-23 09:22:10 UTC
Tier daemon has been moved to the gluster service framework where all the tier commands are with the syntax "gluster v tier ....."  This old command of tier has to be removed as it is not being used widely, it falls under rebalance and creates confusion, and also because with the support of this command we will be able to spawn two tier processes. Spawning two tier processes is an issue. for more details refer [1]

As the command itself has to be removed, it doesn't make much sense fixing it and then removing it.

IMO we can close this bug. If there is something that I'm missing, do let me know. 

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1415590

Comment 3 Kaushal 2017-03-08 10:50:48 UTC
This bug is getting closed because GlusteFS-3.7 has reached its end-of-life.

Note: This bug is being closed using a script. No verification has been performed to check if it still exists on newer releases of GlusterFS.
If this bug still exists in newer GlusterFS releases, please reopen this bug against the newer release.