Bug 1470938

Summary:	Regression: non-disruptive(in-service) upgrade on EC volume fails
Product:	[Community] GlusterFS	Reporter:	Sunil Kumar Acharya <sheggodu>
Component:	disperse	Assignee:	bugs <bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	3.11	CC:	amukherj, aspandey, bugs, nchilaka, pkarampu, rhinduja, rhs-bugs, sheggodu, storage-qa-internal
Target Milestone:	---	Keywords:	Regression
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.11.2	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1468261	Environment:
Last Closed:	2017-08-12 13:07:33 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:	1468261
Bug Blocks:	1465289

Comment 1 Worker Ant 2017-07-14 07:36:34 UTC

REVIEW: https://review.gluster.org/17773 (cluster/ec: Non-disruptive upgrade on EC volume fails) posted (#1) for review on release-3.11 by Sunil Kumar Acharya (sheggodu)

Comment 2 Worker Ant 2017-07-19 11:26:25 UTC

COMMIT: https://review.gluster.org/17773 committed in release-3.11 by Shyamsundar Ranganathan (srangana) 
------
commit 425c5acca90bd8c00b94cdcd5082ccc7c1ba078b
Author: Sunil Kumar Acharya <sheggodu>
Date:   Wed Jul 5 16:41:38 2017 +0530

    cluster/ec: Non-disruptive upgrade on EC volume fails
    
    Problem:
    Enabling optimistic changelog on EC volume was not
    handling node down scenarios appropriately resulting
    in volume data inaccessibility.
    
    Solution:
    Update dirty xattr appropriately on good bricks whenever
    nodes are down. This would fix the metadata information
    as part of heal and thus ensures data accessibility.
    
    >BUG: 1468261
    >Change-Id: I08b0d28df386d9b2b49c3de84b4aac1c729ac057
    >Signed-off-by: Sunil Kumar Acharya <sheggodu>
    >Reviewed-on: https://review.gluster.org/17703
    >Smoke: Gluster Build System <jenkins.org>
    >CentOS-regression: Gluster Build System <jenkins.org>
    >Reviewed-by: Pranith Kumar Karampuri <pkarampu>
    
    BUG: 1470938
    Change-Id: I08b0d28df386d9b2b49c3de84b4aac1c729ac057
    Signed-off-by: Sunil Kumar Acharya <sheggodu>
    Reviewed-on: https://review.gluster.org/17773
    Smoke: Gluster Build System <jenkins.org>
    Reviewed-by: Ashish Pandey <aspandey>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu>
    CentOS-regression: Gluster Build System <jenkins.org>
    NetBSD-regression: NetBSD Build System <jenkins.org>

Comment 3 Shyamsundar 2017-08-12 13:07:33 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.2, please open a new bug report.

glusterfs-3.11.2 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/gluster-users/2017-July/031908.html
[2] https://www.gluster.org/pipermail/gluster-users/