Image perpetually in "SAVING" state if snapshot fails to create
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Invalid
|
Medium
|
Unassigned |
Bug Description
If a user tries to create an image from a snapshot (e.g., through Horizon), and the process of creating a snapshot fails (e.g., nova fails to extract the KVM snapshot to a disk because there isn't enough room in the temp directory), then the resulting entry in "nova image-list" will always be in the "SAVING" state.
It would be easier for ops to identify that a problem has occurred with the snapshot process if, when a failure like this occurred, the state of the new image was changed to some kind of error state.
I encountered this problem with essex, but looking at the code in trunk as of today, it doesn't look like there's any exception handling code in nova/libvirt/
description: | updated |
description: | updated |
Changed in nova: | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in nova: | |
milestone: | none → grizzly-rc1 |
Changed in nova: | |
milestone: | grizzly-rc1 → none |
I think this is a duplicate of bug #1064386