Bug 1331226

Summary:	Cloned volume is not cleaned up on deletion
Product:	[Community] GlusterFS	Reporter:	Luis Pabón <lpabon>
Component:	snapshot	Assignee:	Avra Sengupta <asengupt>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	high	Docs Contact:
Priority:	medium
Version:	3.7.11	CC:	bugs, hgowtham, madam
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-10-21 10:06:44 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 Luis Pabón 2016-04-28 03:24:23 UTC

Description of problem:
Once a cloned volume is deleted, there should be a way to destroy it and remove all the mount points and logical volumes created by GlusterFS

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


How reproducible:
100%

Steps to Reproduce:
- gluster volume create myvol ...
- gluster snapshot create mysnap myvol
- gluster snapshot activate mysnap
- gluster snapshot clone myclone mysnap
- gluster snapshot deactivate mysnap
- gluster snapshot delete mysnap 
- gluster volume delete myclone


Actual results:
All LVs are still mounted and space still allocated in thin pools

Expected results:
All LVs unmounted and destroyed to return space back to thin pools.

or do one more command to fully destroy:

- gluster snapshot clone destroy myclone

Additional info:

Comment 1 Avra Sengupta 2016-10-21 10:06:44 UTC

The behaviour of snapshot clone is in sync with current volume delete's behaviour where we do not cleanup the volume's bricks, irrespective of how the bricks were created (be it user created or snapshot restored).

I believe that is the right thing to do, as we do not want to mess up with users backend data. Closing it as it's not a bug, but an expected behaviour.