Bug 1272968

Summary: glusterfs vol based layout: Deleting a share created from snapshot should also delete its backend gluster volume
Product: [Community] RDO Reporter: krishnaram Karthick <kramdoss>
Component: openstack-manilaAssignee: Pete Zaitcev <zaitcev>
Status: CLOSED EOL QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: Liberty   
Target Milestone: ---   
Target Release: Kilo   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-05-19 15:50:23 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 krishnaram Karthick 2015-10-19 10:19:52 UTC 
Description of problem:

When a share is created from snapshot, a snap clone volume is created in the backend gluster cluster. However, when we delete the same share the backend volume created isn't deleted. The volume would remain dangling in the volume pool un-managed.

Hence, whenever a share created from snapshot is deleted, its corresponding backend gluster volume should also be deleted.

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

# rpm -qa | grep 'manila'
python-manila-1.0.0.0-rc2.dev24.el7.centos.noarch
python-manilaclient-1.4.1-dev3.el7.centos.noarch
openstack-manila-1.0.0.0-rc2.dev24.el7.centos.noarch
openstack-manila-share-1.0.0.0-rc2.dev24.el7.centos.noarch


How reproducible:
Always

Steps to Reproduce:
1. create a manila share from glusterfs backend using vol mapped layout
2. create a snapshot of the share
3. create a share out of the snapshot created
4. delete the share created out of snapshot --> this doesn't delete the backend gluster volume

Actual results:
deleting share from snapshot doesn't delete its corresponding backend gluster volume.

Expected results:

backend gluster volume has to be deleted

Additional info:
Comment 1 Chandan Kumar 2016-05-19 15:50:23 UTC 
This bug is against a Version which has reached End of Life.
If it's still present in supported release (http://releases.openstack.org), please update Version and reopen.