Bug 1259607 - Data Tiering: rebalance tier stop cli command not working
Summary: Data Tiering: rebalance tier stop cli command not working
Keywords:
Status: CLOSED EOL
Alias: None
Product: GlusterFS
Classification: Community
Component: tiering
Version: 3.7.5
Hardware: Unspecified
OS: Unspecified
urgent
low
Target Milestone: ---
Assignee: Dan Lambright
QA Contact: bugs@gluster.org
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-09-03 07:39 UTC by Arthy Loganathan
Modified: 2020-05-27 12:24 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-08 10:58:00 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Arthy Loganathan 2015-09-03 07:39:11 UTC
Description of problem:
rebalance tier stop cli command not working

Version-Release number of selected component (if applicable):
glusterfs-fuse-3.7.3-0.93

How reproducible:
Always

Steps to Reproduce:
1. Run the command,
[root@node31 ~]# gluster volume rebalance testvol tier stop
Usage: volume rebalance <VOLNAME> {{fix-layout start} | {start [force]|stop|status}}


Actual results:
rebalance tier stop cli command is not working

Expected results:
CLI command should succeed and rebalance on tiered volume should stop

Additional info:

Comment 1 Mohammed Rafi KC 2015-09-05 06:48:38 UTC
Currently we are not supporting tier stop command. But we can take this as RFE if it is marked as high priority.

Comment 3 Kaushal 2017-03-08 10:58:00 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.

Comment 4 Arthy Loganathan 2020-05-27 12:24:21 UTC
Clearing this needinfo , as this bug is closed already due to EOL of the component.


Note You need to log in before you can comment on or make changes to this bug.