Bug 1296108

Summary:	xattrs on directories are unavailable on distributed replicated volume after adding new bricks
Product:	[Community] GlusterFS	Reporter:	Susant Kumar Palai <spalai>
Component:	distribute	Assignee:	bugs <bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	3.7.7	CC:	ahatfiel, bhubbard, bkunal, bugs, mmalhotr, mnapolis, nbalacha, rgowdapp, sankarshan, sasundar, smohan, spalai, storage-qa-internal
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	glusterfs-3.7.7	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1287539	Environment:
Last Closed:	2016-04-19 07:52:37 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:	1287539
Bug Blocks:	1285167

Comment 1 Vijay Bellur 2016-01-06 10:56:45 UTC

REVIEW: http://review.gluster.org/13184 (cluster/dht: Handle failure in getxattr) posted (#1) for review on release-3.7 by Susant Palai (spalai)

Comment 2 Vijay Bellur 2016-01-20 07:00:13 UTC

REVIEW: http://review.gluster.org/13184 (cluster/dht: Handle failure in getxattr) posted (#2) for review on release-3.7 by Pranith Kumar Karampuri (pkarampu)

Comment 3 Vijay Bellur 2016-01-25 02:28:00 UTC

COMMIT: http://review.gluster.org/13184 committed in release-3.7 by Pranith Kumar Karampuri (pkarampu) 
------
commit f3426ccc95133f8b5c946f98867090c636305d6e
Author: Susant Palai <spalai>
Date:   Wed Dec 2 04:59:55 2015 -0500

    cluster/dht: Handle failure in getxattr
    
    Problem: Currently even if we have received xattrs from any one of
    the subvolume, we unwind with error in case the last subvol (which
    unwinds) received a negative response.
    
    To handle the case check if any of the subvolume has received
    a response and pass it down.
    
    BUG: 1296108
    Change-Id: I5279442fabd500934d04509d83ae87fdd69388e2
    Signed-off-by: Susant Palai <spalai>
    Reviewed-on: http://review.gluster.org/12845
    Tested-by: NetBSD Build System <jenkins.org>
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Raghavendra G <rgowdapp>
    Signed-off-by: Susant Palai <spalai>
    Reviewed-on: http://review.gluster.org/13184
    Reviewed-by: Pranith Kumar Karampuri <pkarampu>
    Tested-by: Pranith Kumar Karampuri <pkarampu>
    Smoke: Gluster Build System <jenkins.com>
    CentOS-regression: Gluster Build System <jenkins.com>
    NetBSD-regression: NetBSD Build System <jenkins.org>

Comment 4 Kaushal 2016-04-19 07:52:37 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.7, please open a new bug report.

glusterfs-3.7.7 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-February/025292.html
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user