Bug 1273716

Summary:	[RFE]: [SNAPSHOT]: snapshot-clone should not be created under /run/gluster/snaps
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Shashank Raj <sraj>
Component:	snapshot	Assignee:	rjoseph
Status:	CLOSED DUPLICATE	QA Contact:	storage-qa-internal <storage-qa-internal>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rhgs-3.1	CC:	asengupt, rhs-bugs, sashinde, storage-qa-internal
Target Milestone:	---	Keywords:	FutureFeature, ZStream
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-07-14 09:17:30 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 Shashank Raj 2015-10-21 06:07:40 UTC

Description of problem:

Currently if we create the clone of a snapshot, the clones gets created under /run/gluster/snaps. Since clone is like a regular volume, there should be a separate path for this like /run/gluster/clones


Version-Release number of selected component (if applicable):
glusterfs-3.7.5-0.3


How reproducible:
Always

Steps to Reproduce:
1.Create a volume and create a snapshot of it.
2.Now create a clone of this snapshot.
3.Observe that the clone is created under /run/gluster/snaps where we have entries for the snapshots.
4.We should have clones created under a separate directory.

Actual results:
Clones are getting created under /run/gluster/snaps


Expected results:
Clones should not be created under /run/gluster/snaps and they should have entries in a separate directory like /run/gluster/clones, since they are just like regular volumes



Additional info:

Comment 2 Avra Sengupta 2016-07-14 09:17:30 UTC

There are no consequences of storing the clones under /run/gluster/snaps pther than the one mentioned in https://bugzilla.redhat.com/show_bug.cgi?id=1273722.
This will be handled as part of the fix for 1273722. Marking this as a duplicate

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