[openstack-dev] [Glance] Regarding Glance's behaviour when updating an image ...

Flavio Percoco flavio at redhat.com
Mon Nov 25 08:10:49 UTC 2013

On 25/11/13 03:23 +0000, David koo wrote:
>Hi All,
>    Newbie stacker here ...
>    I have a basic question regarding the indended behaviour of Glance's
>image update API: What is the indended behaviour of Glance when updating
>an already uploaded image file?
>    The functional test indicates that the intended behaviour is to
>disallow such updates:
>        glance/tests/v2/test_images.py:test_image_lifecycle:210
>            # Uploading duplicate data should be rejected with a 409
>            ...
>    When I configure Glance to use the local filesystem backend I do
>indeed get a 409 conflict but when I configure Glance to use Swift as
>the backend the operation succeeds and the original image file is
>    On a related note, when using the local filesystem backend though I
>get a 409 conflict, it leaves the image in the "saving" state - I think
>it shouldn't change the state of the image. There's a bug logged
>regarding this behaviour (bug 1241379) and I'm working on the fix. But
>in light of the above question perhaps I should file another bug
>regarding the Swift storage backend?

As you mentioned, there seems to be a bug in the swift backend. Images
are immutable.

Thanks for raising this.


Flavio Percoco
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20131125/33d71687/attachment.pgp>

More information about the OpenStack-dev mailing list