glusterfs: Rebased snapshot volume is not deleted
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
Medium
|
Thang Pham | ||
Icehouse |
Fix Released
|
Medium
|
Chuck Short |
Bug Description
When deleting a volume that was snapshot, the volume is not properly deleted.
Steps to recreate bug:
1. Create a volume
2. Attach volume to a running instance.
3. Take an online snapshot of the volume.
Note that the active volume used by the instance is now switched to volume-
4. Delete the snapshot.
The snapshot volume will be rebased, and the "active" volume as seen in volume-<uuid>.info is now set to
volume-
Under the glusterfs mount point, there are now only 2 files related to the volume:
- volume-<uuid>.info
- volume-
The original volume base volume-<uuid> is deleted after the rebase.
5. Detach the volume from the running instance.
6. Delete the volume.
Under the glusterfs mount point, the volume-
Changed in cinder: | |
assignee: | nobody → Thang Pham (thang-pham) |
tags: | added: drivers |
Changed in cinder: | |
status: | New → In Progress |
milestone: | none → next |
importance: | Undecided → Low |
Changed in cinder: | |
milestone: | next → juno-1 |
tags: | added: icehouse-backport-potential |
Changed in cinder: | |
importance: | Low → Medium |
tags: | removed: icehouse-backport-potential |
Changed in cinder: | |
status: | Fix Committed → Fix Released |
Changed in cinder: | |
milestone: | juno-1 → 2014.2 |
Fix proposed to branch: master /review. openstack. org/86158
Review: https:/