restarting cinder-volume doesn't help volume and snapshot which status is creating
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
Medium
|
Ivan Kolodyazhny |
Bug Description
When restart cinder-volume process, this should change volume
and snapshot status to valid status.
How to reproduce?
1. Request create volume API.
2. Unfortunately, cinder-volume process down, after the request.
3. Remain creating status volume.
4. With restarting of cinder-volume doesn't move this status forward.
What is the expected result?
Restarting cinder-volume process make this halfway volume to 'error' status.
(None -> creating -> error)
Others:
This report is also same to snapshot.
I know that I can delete this 'creating' volume with force-delete command.
However, consistent with nova, from point of restarting process,
transition to error status is needed, I think.
Changed in cinder: | |
status: | New → In Progress |
assignee: | nobody → haruka tanizawa (h-tanizawa) |
Changed in cinder: | |
assignee: | haruka tanizawa (h-tanizawa) → nobody |
Changed in cinder: | |
status: | In Progress → New |
description: | updated |
Changed in cinder: | |
assignee: | Yasuaki Nagata (yasuaki-nagata) → Ivan Kolodyazhny (e0ne) |
Changed in cinder: | |
importance: | Undecided → Medium |
Changed in cinder: | |
milestone: | none → kilo-rc1 |
status: | Fix Committed → Fix Released |
Changed in cinder: | |
milestone: | kilo-rc1 → 2015.1.0 |
Should I separate this bug into volume and snapshot in this case??