Bug 1286572 - [FEAT] DHT - rebalance - rebalance status o/p should be different for 'fix-layout' option, it should not show 'Rebalanced-files' , 'Size', 'Scanned' etc as it is not migrating any files.
[FEAT] DHT - rebalance - rebalance status o/p should be different for 'fix-la...
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: distribute (Show other bugs)
x86_64 Linux
medium Severity medium
: ---
: RHGS 3.2.0
Assigned To: Nithya Balachandran
Prasad Desala
triaged, dht-rebalance-usability, dht...
: FutureFeature
Depends On: 890640
Blocks: 1351503 1351530
  Show dependency treegraph
Reported: 2015-11-30 04:33 EST by Susant Kumar Palai
Modified: 2017-12-05 01:53 EST (History)
12 users (show)

See Also:
Fixed In Version: glusterfs-3.8.4-1
Doc Type: Enhancement
Doc Text:
Previously, the output of the 'gluster volume rebalance VOLNAME status' command attempted to display status details for fix-layout operations despite this operation not populating the output with details of rebalanced files, scanned files, failures, and size. The unpopulated sections have now been removed so that only status and elapsed time on each node are shown.
Story Points: ---
Clone Of: 890640
Last Closed: 2017-03-23 01:25:17 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Comment 8 Prasad Desala 2016-11-25 02:03:06 EST
Verified this BZ on glusterfs version: 3.8.4-5.el7rhgs.x86_64.

When rebalance is started with fix-layout option, the rebalance status output is now showing the status of layout fixing.

Moving this BZ to Verified, will raise a new BZ if any on this separately.
Comment 12 errata-xmlrpc 2017-03-23 01:25:17 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


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