Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1065626 - Rebalance stop on a distributed-replicated volume shows wrong message on cli
Summary: Rebalance stop on a distributed-replicated volume shows wrong message on cli
Keywords:
Status: CLOSED EOL
Alias: None
Product: GlusterFS
Classification: Community
Component: distribute
Version: 3.5.6
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Nithya Balachandran
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-15 08:26 UTC by Anoop C S
Modified: 2016-06-17 16:23 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-17 16:23:25 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:


Attachments (Terms of Use)

Description Anoop C S 2014-02-15 08:26:15 UTC
Description of problem:

Even if rebalance is not initiated on a distribute-replicate volume, cli displays rebalance is success. 


Version-Release number of selected component (if applicable):
3.5beta3

How reproducible:


Steps to Reproduce:
1. create a 2x2 dist-replicat volume
2. Start the volume
3. Run "gluster volume rebalance $vol stop"

Actual results:

volume rebalance: disrep2: success: rebalance process may be in the middle of a file migration.
The process will be fully stopped once the migration of the file is complete.
Please check rebalance process for completion before doing any further brick related tasks on the volume.

Expected results:

Rebalance is not running on the volume disrep2

Additional info:

Comment 2 Niels de Vos 2016-06-17 16:23:25 UTC
This bug is getting closed because the 3.5 is marked End-Of-Life. There will be no further updates to this version. Please open a new bug against a version that still receives bugfixes if you are still facing this issue in a more current release.


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