Bug 1340992

Summary:	Directory creation(mkdir) fails when the remove brick is initiated for replicated volumes accessing via nfs-ganesha
Product:	[Community] GlusterFS	Reporter:	Pranith Kumar K <pkarampu>
Component:	replicate	Assignee:	Pranith Kumar K <pkarampu>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	3.7.11	CC:	amukherj, bugs, jthottan, kkeithle, ndevos, pkarampu, rcyriac, rgowdapp, rhinduja, skoduri, sraj, storage-qa-internal
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	glusterfs-3.7.12	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1340623	Environment:
Last Closed:	2016-06-28 12:18:56 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:	1340085, 1340623, 1342178
Bug Blocks:	1311817

Comment 1 Vijay Bellur 2016-06-03 07:17:32 UTC

REVIEW: http://review.gluster.org/14633 (cluster/afr: Unwind xdata_rsp even in case of failures) posted (#1) for review on release-3.7 by Pranith Kumar Karampuri (pkarampu)

Comment 2 Vijay Bellur 2016-06-03 13:24:04 UTC

COMMIT: http://review.gluster.org/14633 committed in release-3.7 by Pranith Kumar Karampuri (pkarampu) 
------
commit 0a012d82717562896831c12103f91839f6269259
Author: Pranith Kumar K <pkarampu>
Date:   Fri May 27 15:47:07 2016 +0530

    cluster/afr: Unwind xdata_rsp even in case of failures
    
    DHT expects GF_PREOP_CHECK_FAILED to be present in xdata_rsp in case of mkdir
    failures because of stale layout. But AFR was unwinding null xdata_rsp in case
    of failures. This was leading to mkdir failures just after remove-brick. Unwind
    the xdata_rsp in case of failures to make sure the response from brick reaches
    dht.
    
     >BUG: 1340623
     >Change-Id: Idd3f7b95730e8ea987b608e892011ff190e181d1
     >Signed-off-by: Pranith Kumar K <pkarampu>
     >Reviewed-on: http://review.gluster.org/14553
     >NetBSD-regression: NetBSD Build System <jenkins.org>
     >Reviewed-by: Ravishankar N <ravishankar>
     >Smoke: Gluster Build System <jenkins.com>
     >CentOS-regression: Gluster Build System <jenkins.com>
     >Reviewed-by: Anuradha Talur <atalur>
     >Reviewed-by: Krutika Dhananjay <kdhananj>
    
    BUG: 1340992
    Change-Id: I2641d35a851be692aa223dfea5d082245ac6c2bc
    Signed-off-by: Pranith Kumar K <pkarampu>
    Reviewed-on: http://review.gluster.org/14633
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.com>
    Smoke: Gluster Build System <jenkins.com>

Comment 3 Kaushal 2016-06-28 12:18:56 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.12, please open a new bug report.

glusterfs-3.7.12 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-devel/2016-June/049918.html
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user