Bug 1299822

Summary:	Snapshot creation fails on a tiered volume
Product:	[Community] GlusterFS	Reporter:	Avra Sengupta <asengupt>
Component:	snapshot	Assignee:	Avra Sengupta <asengupt>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	3.7.7	CC:	annair, bugs, byarlaga, hgowtham, rjoseph, sanandpa, storage-qa-internal
Target Milestone:	---	Keywords:	Triaged, ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.7.7	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1299819	Environment:
Last Closed:	2016-02-15 12:15:41 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:	1299799, 1299819
Bug Blocks:

Comment 1 Vijay Bellur 2016-01-19 11:31:26 UTC

REVIEW: http://review.gluster.org/13261 (snapshot: Return before redundant quorum check) posted (#1) for review on release-3.7 by Avra Sengupta (asengupt)

Comment 2 Vijay Bellur 2016-01-20 06:57:30 UTC

COMMIT: http://review.gluster.org/13261 committed in release-3.7 by Pranith Kumar Karampuri (pkarampu) 
------
commit b273915811fc484698a46f36597581dd0a5753e7
Author: Avra Sengupta <asengupt>
Date:   Tue Jan 19 16:22:17 2016 +0530

    snapshot: Return before redundant quorum check
    
        Backport of http://review.gluster.org/#/c/13260/
    
    As of today, we don't support creation of snapshot even
    if one brick is down. Hence the older quorum check is
    redundant. Returning after performing the check to
    see if all bricks are up.
    
    Change-Id: I35661d05a15be0109aaae51b4fe0d5a8ca4333ad
    BUG: 1299822
    Signed-off-by: Avra Sengupta <asengupt>
    Reviewed-on: http://review.gluster.org/13261
    Smoke: Gluster Build System <jenkins.com>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.com>
    Reviewed-by: Rajesh Joseph <rjoseph>

Comment 3 Kaushal 2016-04-19 07:52:59 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