Bug 1315141

Summary:	RFE: "heal" commands output should have a fixed fields
Product:	[Community] GlusterFS	Reporter:	Pranith Kumar K <pkarampu>
Component:	replicate	Assignee:	Pranith Kumar K <pkarampu>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	3.7.9	CC:	atalur, bugs, ravishankar, smohan, spandura
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.7.10	Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:	1297897	Environment:
Last Closed:	2016-04-19 06:59: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:	1297897
Bug Blocks:

Comment 1 Vijay Bellur 2016-03-07 03:19:57 UTC

REVIEW: http://review.gluster.org/13616 (heal: Have fixed number of fields in heal info output) posted (#1) for review on release-3.7 by Pranith Kumar Karampuri (pkarampu)

Comment 2 Vijay Bellur 2016-03-18 06:44:55 UTC

COMMIT: http://review.gluster.org/13616 committed in release-3.7 by Pranith Kumar Karampuri (pkarampu) 
------
commit 0b4f733f5ef074a38dacd33b39e5371d467d0f25
Author: Pranith Kumar K <pkarampu>
Date:   Mon Dec 21 17:55:49 2015 +0530

    heal: Have fixed number of fields in heal info output
    
    Sample output:
    ⚡ gluster v heal r2 info
    Brick localhost.localdomain:/home/gfs/r2_0
    /a
    /
    Status: Connected
    Number of entries: 2
    
    Brick localhost.localdomain:/home/gfs/r2_1
    Status: Transport endpoint is not connected
    Number of entries: -
    
    Brick localhost.localdomain:/home/gfs/r2_2
    Status: Connected
    Number of entries: 0
    
    Brick localhost.localdomain:/home/gfs/r2_3
    Status: Connected
    Number of entries: 0
    
    Partial failure will print:
    ...
    <gfid:3efb51cf-5fa5-4bed-817b-afd600e9449e>
    Status: Failed to process entries completely. (Transport endpoint is not connected)
    Number of entries: 372
    ...
    
     >BUG: 1297897
     >Change-Id: I79131cbf255acd98f11eedafb53246c465f6665d
     >Signed-off-by: Pranith Kumar K <pkarampu>
     >Reviewed-on: http://review.gluster.org/13231
     >Smoke: Gluster Build System <jenkins.com>
     >Reviewed-by: Krutika Dhananjay <kdhananj>
     >Reviewed-by: Sahina Bose <sabose>
     >NetBSD-regression: NetBSD Build System <jenkins.org>
     >CentOS-regression: Gluster Build System <jenkins.com>
    
    BUG: 1315141
    Change-Id: I98de851b86598bb9c98e6203f855b69b585e2271
    Signed-off-by: Pranith Kumar K <pkarampu>
    Reviewed-on: http://review.gluster.org/13616
    Smoke: Gluster Build System <jenkins.com>
    CentOS-regression: Gluster Build System <jenkins.com>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    Reviewed-by: Ravishankar N <ravishankar>

Comment 3 Kaushal 2016-04-19 06:59:23 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.7.10, please open a new bug report.

glusterfs-3.7.10 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] https://www.gluster.org/pipermail/gluster-users/2016-April/026164.html
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user