Image perpetually in "SAVING" state if snapshot fails to create
Bug #1076019 reported by
Lorin Hochstein
This bug report is a duplicate of:
Bug #1555065: Image goes to saving state when we delete instance just after taking snapshot and remain the state forever.
Edit
Remove
This bug affects 2 people
| 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 |
Revision history for this message
| Giampaolo Lauria (lauria) wrote | #1 |
| Changed in nova: | |
| status: | Triaged → Invalid |
| Changed in nova: | |
| milestone: | grizzly-rc1 → none |
To post a comment you must log in.
I think this is a duplicate of bug #1064386