Undeletable temporary volume object is left in DB if volume migration fails
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
High
|
Mitsuhiro Tanino | ||
Juno |
Fix Released
|
High
|
Mitsuhiro Tanino |
Bug Description
When some error happens during volume migration (e.g. https:/
Steps to reproduce:
Having https:/
$ cinder create --name vol1 1
$ cinder migrate vol1 somehost@
Verify that it failed as described in https:/
Expected result:
No new volumes are left in db or they can be deleted.
Actual result:
Temporary volume is left in DB, cannot be deleted through API.
Real shell log: http://
Changed in cinder: | |
assignee: | krishna (leburu-reddy) → nobody |
Changed in cinder: | |
importance: | Undecided → High |
tags: | added: lvm migration |
Changed in cinder: | |
milestone: | none → kilo-3 |
status: | Fix Committed → Fix Released |
Changed in cinder: | |
milestone: | kilo-3 → 2015.1.0 |
The status of the volumes in the database is changed from available to deleted ,when the migration failed volume is deleted.
The id is present in the database but in deleted state.