Bug 1089527

Summary:	[SNAPSHOT]: Able to create snapshot when one of the brick is down even without force
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Rahul Hinduja <rhinduja>
Component:	snapshot	Assignee:	Joseph Elwin Fernandes <josferna>
Status:	CLOSED ERRATA	QA Contact:	Rahul Hinduja <rhinduja>
Severity:	high	Docs Contact:
Priority:	high
Version:	rhgs-3.0	CC:	josferna, nsathyan, racpatel, rhs-bugs, sankarshan, senaik, ssamanta, storage-qa-internal
Target Milestone:	---
Target Release:	RHGS 3.0.0
Hardware:	x86_64
OS:	Linux
Whiteboard:	SNAPSHOT
Fixed In Version:	glusterfs-3.6.0-4.0.el6rhs	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1090042 (view as bug list)		Environment:
Last Closed:	2014-09-22 19:35:51 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:
Bug Blocks:	1083502, 1090042

Description Rahul Hinduja 2014-04-20 10:59:59 UTC

Description of problem:
=======================
we decided to fail the snapshot create when any of the brick is down until force is applied to the CLI. But when a brick is down, I am able to create a snapshot of a volume.

[root@snapshot09 ~]# gluster volume status vol3
Status of volume: vol3
Gluster process                                         Port    Online  Pid
------------------------------------------------------------------------------
Brick snapshot09.lab.eng.blr.redhat.com:/brick3/b3      49155   Y       12498
Brick snapshot10.lab.eng.blr.redhat.com:/brick3/b3      N/A     N       9069
Brick snapshot11.lab.eng.blr.redhat.com:/brick3/b3      49155   Y       5187
Brick snapshot12.lab.eng.blr.redhat.com:/brick3/b3      49155   Y       5082
NFS Server on localhost                                 2049    Y       13272
Self-heal Daemon on localhost                           N/A     Y       13279
NFS Server on snapshot10.lab.eng.blr.redhat.com         2049    Y       9761
Self-heal Daemon on snapshot10.lab.eng.blr.redhat.com   N/A     Y       9768
NFS Server on snapshot11.lab.eng.blr.redhat.com         2049    Y       5842
Self-heal Daemon on snapshot11.lab.eng.blr.redhat.com   N/A     Y       5849
NFS Server on snapshot12.lab.eng.blr.redhat.com         2049    Y       5738
Self-heal Daemon on snapshot12.lab.eng.blr.redhat.com   N/A     Y       5745
 
Task Status of Volume vol3
------------------------------------------------------------------------------
There are no active volume tasks
 
[root@snapshot09 ~]# gluster snapshot create rrr1 vol3
snapshot create: rrr1: snap created successfully
[root@snapshot09 ~]# 
[root@snapshot09 ~]# 
[root@snapshot09 ~]# gluster snapshot list vol3
rrr1
[root@snapshot09 ~]# 



Version-Release number of selected component (if applicable):
=============================================================

glusterfs-libs-3.5qa2-0.340.gitc193996.el6rhs.x86_64


How reproducible:
=================
1/1


Steps to Reproduce:
===================
1. Create and start volume
2. Kill one of the brick of volume
3. Create a snapshot of a volume

Actual results:
===============

Snapshot creation is successful.


Expected results:
=================
Snapshot creation should fail until force is applied.

Comment 1 Nagaprasad Sathyanarayana 2014-04-21 06:17:56 UTC

Marking snapshot BZs to RHS 3.0.

Comment 2 Joseph Elwin Fernandes 2014-04-22 03:49:38 UTC

Fixed in http://review.gluster.org/#/c/7520/

Comment 3 rjoseph 2014-05-14 10:58:58 UTC

*** Bug 1089531 has been marked as a duplicate of this bug. ***

Comment 4 Nagaprasad Sathyanarayana 2014-05-19 10:56:34 UTC

Setting flags required to add BZs to RHS 3.0 Errata

Comment 6 senaik 2014-05-20 09:05:38 UTC

Version : glusterfs-3.6.0.4-1.el6rhs.x86_64
========

When one brick is down, snapshot creation fails with the below message : 

 gluster snap create snap2 vol0
snapshot create: failed: brick 10.70.44.54:/brick0/b0 is not started. Please start the stopped brick and then issue snapshot create command or use [force] option in snapshot create to override this behavior.
Snapshot command failed

Marking the bug as 'Verified'

Comment 8 errata-xmlrpc 2014-09-22 19:35:51 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2014-1278.html