yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #52925
[Bug 1076019] Re: Image perpetually in "SAVING" state if snapshot fails to create
*** This bug is a duplicate of bug 1555065 ***
https://bugs.launchpad.net/bugs/1555065
** This bug is no longer a duplicate of bug 1064386
Image stays in Saving State if any error occurs while snapshotting an instance
** This bug has been marked a duplicate of bug 1555065
Image goes to saving state when we delete instance just after taking snapshot and remain the state forever
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1076019
Title:
Image perpetually in "SAVING" state if snapshot fails to create
Status in OpenStack Compute (nova):
Invalid
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/driver.py:snapshot when snapshot.extract fails.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1076019/+subscriptions