Bug 1058569

Summary:	Openstack glance image corruption after remove-brick/rebalance on the Gluster nodes
Product:	[Community] GlusterFS	Reporter:	Shyamsundar <srangana>
Component:	distribute	Assignee:	Nagaprasad Sathyanarayana <nsathyan>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, gluster-bugs, nlevinki, rwheeler, smanjara, smohan, vagarwal, vbellur
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.6.0beta1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1054782	Environment:
Last Closed:	2014-11-11 08:27:19 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:

Comment 1 Anand Avati 2014-01-28 05:46:47 UTC

REVIEW: http://review.gluster.org/6830 (cluster/dht: Set restrictive open flags for files under rebalance) posted (#1) for review on master by Shyamsundar Ranganathan (srangana)

Comment 2 Anand Avati 2014-02-04 17:57:07 UTC

COMMIT: http://review.gluster.org/6830 committed in master by Vijay Bellur (vbellur) 
------
commit 0c721c4c046d3580f7774eb480ff139c3ef814b5
Author: ShyamsundarR <srangana>
Date:   Tue Jan 28 11:09:10 2014 +0530

    cluster/dht: Set restrictive open flags for files under rebalance
    
    Files that are being rebalanced are created in the new volume
    and access path needs to open these files to write changing
    data in parallel to both the old and new locations. While opening
    the file in the new location, we need to restrict the open flags
    to not use truncate or create and fail if exist flags, to prevent
    open failures or inadvertently truncate the file under rebalance.
    
    Change-Id: I12130e0377adc393f1925c45585200ad991fd0d5
    BUG: 1058569
    Signed-off-by: ShyamsundarR <srangana>
    Reviewed-on: http://review.gluster.org/6830
    Reviewed-by: Raghavendra G <rgowdapp>
    Reviewed-by: Krutika Dhananjay <kdhananj>
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Raghavendra Bhat <raghavendra>
    Reviewed-by: Vijay Bellur <vbellur>

Comment 4 Niels de Vos 2014-09-22 12:35:21 UTC

A beta release for GlusterFS 3.6.0 has been released. Please verify if the release solves this bug report for you. In case the glusterfs-3.6.0beta1 release does not have a resolution for this issue, leave a comment in this bug and move the status to ASSIGNED. If this release fixes the problem for you, leave a note and change the status to VERIFIED.

Packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update (possibly an "updates-testing" repository) infrastructure for your distribution.

[1] http://supercolony.gluster.org/pipermail/gluster-users/2014-September/018836.html
[2] http://supercolony.gluster.org/pipermail/gluster-users/

Comment 5 Niels de Vos 2014-11-11 08:27:19 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.6.1, please reopen this bug report.

glusterfs-3.6.1 has been announced [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://supercolony.gluster.org/pipermail/gluster-users/2014-November/019410.html
[2] http://supercolony.gluster.org/mailman/listinfo/gluster-users