Bug 1299819

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:	unspecified
Version:	mainline	CC:	annair, bugs, byarlaga, rjoseph, sanandpa, storage-qa-internal
Target Milestone:	---	Keywords:	ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.8rc2	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1299799
Clones:	1299822 (view as bug list)		Environment:
Last Closed:	2016-06-16 13:55:08 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
Bug Blocks:	1299822

Comment 1 Vijay Bellur 2016-01-19 10:55:40 UTC

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

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

COMMIT: http://review.gluster.org/13260 committed in master by Rajesh Joseph (rjoseph) 
------
commit de276bd2452302e2e27b94b7f577c25fc351037d
Author: Avra Sengupta <asengupt>
Date:   Tue Jan 19 16:22:17 2016 +0530

    snapshot: Return before redundant quorum check
    
    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.
    
    BUG: 1299819
    Change-Id: I35661d05a15be0109aaae51b4fe0d5a8ca4333ad
    Signed-off-by: Avra Sengupta <asengupt>
    Reviewed-on: http://review.gluster.org/13260
    Smoke: Gluster Build System <jenkins.com>
    CentOS-regression: Gluster Build System <jenkins.com>
    Reviewed-by: Rajesh Joseph <rjoseph>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    Reviewed-by: mohammed rafi  kc <rkavunga>

Comment 3 Niels de Vos 2016-06-16 13:55:08 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.8.0, please open a new bug report.

glusterfs-3.8.0 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://blog.gluster.org/2016/06/glusterfs-3-8-released/
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user