Bug 1333243

Summary:	[AFR]: "volume heal info" command is failing during in-service upgrade to latest.
Product:	[Community] GlusterFS	Reporter:	Anuradha <atalur>
Component:	replicate	Assignee:	bugs <bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	3.8.0	CC:	asrivast, atalur, bsrirama, bugs, byarlaga, pkarampu, rhinduja, smohan
Target Milestone:	---	Keywords:	ZStream
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	glusterfs-3.8rc2	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1332798	Environment:
Last Closed:	2016-06-16 14:05:07 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:	1311362, 1332798
Bug Blocks:	1268895, 1299184, 1333239

Comment 1 Vijay Bellur 2016-05-05 05:31:49 UTC

REVIEW: http://review.gluster.org/14219 (heal: Fix incorrect heal info output) posted (#1) for review on release-3.8 by Anuradha Talur (atalur)

Comment 2 Vijay Bellur 2016-05-06 14:26:55 UTC

COMMIT: http://review.gluster.org/14219 committed in release-3.8 by Niels de Vos (ndevos) 
------
commit 2ceb471d369c7da89d14c755b759b9358e035ccb
Author: Anuradha Talur <atalur>
Date:   Wed May 4 11:55:43 2016 +0530

    heal: Fix incorrect heal info output
    
    Problem:
    In heterogenous clusters, heal info gives incorrect
    outout as "Failed to process entries completely.
    Number of entries so far: 0".
    
    This happens when the getxattr on virtual xattr
    for <brickpath>/.glusterfs/indices/dirty fails
    on older bricks as they do not recognize the xattr.
    
    Fix:
    Ignore that error so that heal info doesn't
    incorrectly report failure.
    
            >BUG: 1332798
            >Signed-off-by: Anuradha Talur <atalur>
            >Reviewed-on: http://review.gluster.org/14199
            >Reviewed-by: Pranith Kumar Karampuri <pkarampu>
            >Tested-by: Pranith Kumar Karampuri <pkarampu>
            >Smoke: Gluster Build System <jenkins.com>
            >NetBSD-regression: NetBSD Build System <jenkins.org>
            >CentOS-regression: Gluster Build System <jenkins.com>
            >Signed-off-by: Anuradha Talur <atalur>
    
    Change-Id: I0d3541ed0594d67c3c3b8568a89a975a100bf6dd
    BUG: 1333243
    Signed-off-by: Anuradha Talur <atalur>
    Reviewed-on: http://review.gluster.org/14219
    Smoke: Gluster Build System <jenkins.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.com>

Comment 3 Niels de Vos 2016-06-16 14:05:07 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.8.0, please open a new bug report.

glusterfs-3.8.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://blog.gluster.org/2016/06/glusterfs-3-8-released/
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user