Bug 1452000

Summary:	Spacing issue in fix-layout status output
Product:	[Community] GlusterFS	Reporter:	ankit <anraj>
Component:	distribute	Assignee:	ankit <anraj>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.11	CC:	anraj, bugs, nbalacha, rhs-bugs, storage-qa-internal, tdesala
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.11.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1437748	Environment:
Last Closed:	2017-05-30 06:30:23 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:
Bug Depends On:	1412045, 1437748
Bug Blocks:

Comment 1 Worker Ant 2017-05-18 08:48:46 UTC

REVIEW: https://review.gluster.org/17327 (dht:Spacing issue in fix-layout o/p) posted (#2) for review on release-3.11 by ankitraj

Comment 2 Worker Ant 2017-05-25 15:06:58 UTC

REVIEW: https://review.gluster.org/17327 (dht:Spacing issue in fix-layout o/p) posted (#3) for review on release-3.11 by Shyamsundar Ranganathan (srangana)

Comment 3 Worker Ant 2017-05-25 21:16:27 UTC

COMMIT: https://review.gluster.org/17327 committed in release-3.11 by Shyamsundar Ranganathan (srangana) 
------
commit 1fd0fd5cc5bdb47d725c8eaaffa78754c3f6ff17
Author: AnkitRaj <anraj>
Date:   Mon May 8 17:52:33 2017 +0530

    dht:Spacing issue in fix-layout o/p
    
    There is a spacing issue in the status output of
    the rebalance fix-layout operations. If the local
    host name is big then we will have spacing issue.
    This is the backport of below given ID.
    
    > Bug 1437748
    > Reviewed-on: https://review.gluster.org/17203
    > Smoke: Gluster Build System <jenkins.org>
    > Tested-by: ankitraj <anraj>
    > NetBSD-regression: NetBSD Build System <jenkins.org>
    > CentOS-regression: Gluster Build System <jenkins.org>
    >Reviewed-by: Jeff Darcy <jeff.us>
    
    Change-Id: I2fcc4fd382723fb7e93cb4d4dad03dae682cc1a8
    BUG: 1452000
    Signed-off-by: AnkitRaj <anraj>
    Reviewed-on: https://review.gluster.org/17327
    Tested-by: ankitraj
    NetBSD-regression: NetBSD Build System <jenkins.org>
    Smoke: Gluster Build System <jenkins.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana>
    Tested-by: Shyamsundar Ranganathan <srangana>
    CentOS-regression: Gluster Build System <jenkins.org>

Comment 4 Shyamsundar 2017-05-30 18:52:40 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.11.0, please open a new bug report.

glusterfs-3.11.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://lists.gluster.org/pipermail/announce/2017-May/000073.html
[2] https://www.gluster.org/pipermail/gluster-users/