glusterfs vol based layout: Deleting a share created from snapshot should also delete its backend gluster volume
Bug #1506298 reported by
karthick
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Shared File Systems Service (Manila) |
Fix Released
|
Undecided
|
Csaba Henk |
Bug Description
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.
Fix proposed to branch: master /review. openstack. org/237454
Review: https:/