Comment 2 for bug 939791

To reproduce the above bug , I considered the following scenario :

1. Upload an image of size 25 MB.

root@OpenstackEssex10:~# glance -A 93aa6ecbcaaa4e178a927035160281bf add name="amitest-image" is_public=true < /root/openstackessex/ubuntuimg/ami-tty/image
==================================================================================================================================================[100%] 13.6M/s, ETA 0h 0m 0s

2. The above command results in an error,

  Failed to add image. Got error:
Data supplied was not valid.
Details: 400 Bad Request

The server could not comply with the request since it is either malformed or otherwise incorrect.

 Failed to activate image. Got error: Data supplied was not valid. Details: 400 Bad Request The server could not comply with the request since it is either malformed or otherwise incorrect. Failed to update image metadata. Got error: Data supplied was not valid. Details: Invalid disk format 'None' for image.
Note: Your image metadata may still be in the registry, but the image's status will likely be 'killed'.

3. The image is Killed in Glance but when I retrieve the list of images using 'nova image-list' the status of the image is SAVING.

4. When glance fails to update the image metadata from SAVING to ACTIVE ,a Rollback is performed on the db transaction.
     As a result the status of the image is SAVING.

5. Along with the Rollback or instead of Rollback ,is there any way to update the image metadata to KILLED using the
     existing method _kill() in glance.