Bug 803971 - Return status is 0 even though rebalance operation was unsuccessful.
Summary: Return status is 0 even though rebalance operation was unsuccessful.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: cli
Version: mainline
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: shylesh
QA Contact: Vijaykumar Koppad
URL:
Whiteboard:
Depends On:
Blocks: 817967
TreeView+ depends on / blocked
 
Reported: 2012-03-16 07:16 UTC by Vijaykumar Koppad
Modified: 2015-12-01 16:45 UTC (History)
3 users (show)

Fixed In Version: glusterfs-3.4.0
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-24 17:53:51 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions: 3.3.0qa42
Embargoed:

Attachments (Terms of Use)

Description Vijaykumar Koppad 2012-03-16 07:16:04 UTC 
Description of problem:
root@vostro:~# gluster volume rebalance doa fix-layout start
Starting rebalance on volume doa has been successful
root@vostro:~# gluster volume rebalance doa fix-layout stop
Usage: volume rebalance <VOLNAME> [fix-layout] {start|stop|status} [force]
root@vostro:~# echo $?
0
root@vostro:~# gluster volume rebalance doa stop
                                    Node Rebalanced-files          size       scanned         status
                               ---------      -----------   -----------   -----------   ------------
    008069aa-cc3a-479a-905b-681c447923f8                0            0            0     completed
Stopped rebalance process on volume doa 


Version-Release number of selected component (if applicable):
[5e50175f56d05ab6c1295b0e0f0c11695e49c277]3.3.

How reproducible:always
Comment 1 Anand Avati 2012-04-24 16:42:10 UTC 
CHANGE: http://review.gluster.com/3216 (cli: Return -1 if fix-layout stop is issued) merged in master by Vijay Bellur (vijay)
Note You need to log in before you can comment on or make changes to this bug.