Open Stack

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
replaced.

    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?

--
Koo