Bug 1272968 - glusterfs vol based layout: Deleting a share created from snapshot should also delete its backend gluster volume
glusterfs vol based layout: Deleting a share created from snapshot should als...
Product: RDO
Classification: Community
Component: openstack-manila (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: Kilo
Assigned To: Pete Zaitcev
Depends On:
  Show dependency treegraph
Reported: 2015-10-19 06:19 EDT by krishnaram Karthick
Modified: 2016-05-19 11:50 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-05-19 11:50:23 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description krishnaram Karthick 2015-10-19 06:19:52 EDT
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'

How reproducible:

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 11:50:23 EDT
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.

Note You need to log in before you can comment on or make changes to this bug.