Hey David,
I noticed the same thing a couple of days ago and had filed this bug:
https://bugs.launchpad.net/glance/+bug/1249409
Glance v2 api should not be allowing re-uploads IMO. Feel free to add to the
comments there.
Thanks,
Iccha
-----Original Message-----
From: "David koo" <david....@huawei.com>
Sent: Sunday, November 24, 2013 10:23pm
To: "OpenStack Development Mailing List" <openstack-dev@lists.openstack.org>
Subject: [openstack-dev] [Glance] Regarding Glance's behaviour when updating an
image ...
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
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
