409 Conflict returned when attempting to create an image after failed snapshot
Bug #892555 reported by
Gabe Westmaas
This bug report is a duplicate of:
Bug #898162: if a snapshot fails, the task state of the instance stays in "image_snapshot".
Edit
Remove
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Confirmed
|
Medium
|
Unassigned |
Bug Description
If a snapshot is not created successfully, but the request was accepted, that instance cannot be snapshotted even if the original problem was fixed.
For example if there was a network interruption during image upload, a subsequent request to create an image will fail with HTTP error code 409. This has been confirmed on Xen only thus far.
This appears to be because the instance task_state is left in "image_snapshot" even though it is no longer snapshotting.
Changed in nova: | |
importance: | Undecided → Medium |
status: | New → Confirmed |
To post a comment you must log in.
I have observerd after failed snapshot,
nova actions command also fails
log :
===
after that execute nova action command on the vm .
it fails with the error
nova-api ERROR log exception 'dict' object is not callable openstack. wsgi): TRACE: Traceback (most recent call last): openstack. wsgi): TRACE: File "/usr/lib/ python2. 6/site- packages/ nova/api/ openstack/ wsgi.py" , line 525, in dispatch openstack. wsgi): TRACE: return controller_ method( req=request, **action_args) openstack. wsgi): TRACE: TypeError: 'dict' object is not callable openstack. wsgi): TRACE: :8774/v1. 1/1/servers/ 1/actions? fresh=132272984 9.23 returned with HTTP 400
(nova.api.
(nova.api.
(nova.api.
(nova.api.
(nova.api.
nova-api INFO wsgi _call_ http:/localhost
~
~