Nexenta volume driver leaves snapshot uremoved
Bug #1246079 reported by
Mikhail Khodos
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Cinder |
Fix Released
|
Undecided
|
Mikhail Khodos | ||
Bug Description
After deletion of a volume which was created by cloning Nexenta backend still contains snapshot used for cloning.
| Changed in cinder: | |
| assignee: | nobody → Mikhail Khodos (hodosmb) |
| status: | New → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to cinder (master) | #1 |
| Changed in cinder: | |
| status: | In Progress → Fix Committed |
| Changed in cinder: | |
| milestone: | none → icehouse-1 |
| status: | Fix Committed → Fix Released |
| Changed in cinder: | |
| milestone: | icehouse-1 → 2014.1 |
To post a comment you must log in.
Reviewed: https:/
Committed: http://
Submitter: Jenkins
Branch: master
commit e7319bcebdc225a
Author: keystone <email address hidden>
Date: Mon Oct 28 12:29:24 2013 -0700
Nexenta: Remove snapshot after volume-clone deletion.
Detect if volume was created via cloning and remove a snapshot from the
appliance if so. Return 'provider_location' to update the volume DB record
after creating a volume via cloning.
Closes-Bug: #1246079
Change-Id: I6c946d34871119