Bug 1062122

Summary:	[SNAPSHOT] : Delete of a particular snapshot command fails in first attempt, But succeeds in second attempt.
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Sachin Pandit <spandit>
Component:	snapshot	Assignee:	rjoseph
Status:	CLOSED DUPLICATE	QA Contact:	Rahul Hinduja <rhinduja>
Severity:	high	Docs Contact:
Priority:	high
Version:	rhgs-3.0	CC:	nlevinki, nsathyan, rhs-bugs, rjoseph, sdharane, storage-qa-internal
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	3.4.1.6.snap.mar25.2014	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-05-14 12:15:06 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:

Description Sachin Pandit 2014-02-06 08:56:21 UTC

Description of problem:
Delete of a particular snapshot command fails in first attempt, But succeeds in second attempt.

Version-Release number of selected component (if applicable):
glusterfs-3.4.1.snap.jan15.2014

How reproducible:
Very often.

Steps to Reproduce:
1. Create a Distribute-replicate volume 
2. Create some snapshots of this volume
3. Try snapshot delete

Actual results:
Fails in first attempt, But succeeds in second attempt.


Expected results:
Snapshot delete should not fail.


Additional info:

Comment 1 Sachin Pandit 2014-02-06 08:57:57 UTC

The delete was failing because of the race condition between process kill and snap volume unmount. unmount was tried even before the brick process was killed.

This issue is fixed in patch : http://review.gluster.org/#/c/6772/

Comment 3 Sachin Pandit 2014-03-11 07:29:36 UTC

This Bug is dependent on Bug 1049353. So moving this bug to assigned state, until Bug 1049353 is resolved.

Comment 4 Sachin Pandit 2014-03-26 05:25:03 UTC

This bug is dependent on Bug 1049353. Same patch fixes both the issue.
http://review.gluster.org/#/c/7123/

Comment 5 Sachin Pandit 2014-03-27 05:23:46 UTC

Bug 1049353 got opened again because of recent changes. Have to investigate the issue. Moving this bug to assigned until the Bug 1049353 is resolved.

Comment 6 rjoseph 2014-05-14 12:15:06 UTC


*** This bug has been marked as a duplicate of bug 1049353 ***