OpenStack Compute (nova)

409 Conflict returned when attempting to create an image after failed snapshot

Bug #892555 reported by Gabe Westmaas
6
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.

Thierry Carrez (ttx)
Changed in nova:
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
Rajesh Battala (rajesh-battala) wrote :

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
(nova.api.openstack.wsgi): TRACE: Traceback (most recent call last):
(nova.api.openstack.wsgi): TRACE: File "/usr/lib/python2.6/site-packages/nova/api/openstack/wsgi.py", line 525, in dispatch
(nova.api.openstack.wsgi): TRACE: return controller_method(req=request, **action_args)
(nova.api.openstack.wsgi): TRACE: TypeError: 'dict' object is not callable
(nova.api.openstack.wsgi): TRACE:
nova-api INFO wsgi _call_ http:/localhost:8774/v1.1/1/servers/1/actions?fresh=1322729849.23 returned with HTTP 400
~
~

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.