glance/bin
Michael Still 7335088d89 Handle images which exist but can't be seen.
If the master and the slave glance have different permissions, you
can end up with a 409 exception at upload. For example:

 - the image is visible to the replication user on the master
 - the image is present on the slave, but not visible to the
   replication user

The replicator checks for the existance of the image by doing a HEAD
on http://server:port/v1/images/uuid and gets a 404 back. It therefore
decides the image doesn't exist and that it should be replicated. It
does a POST for that URL, and gets a 409 back saying that UUID is
already in use.

Resolves bug 1030396.

Change-Id: Id5fdb7977692593fd6c2e203f0440d4aa5339d92
2012-08-04 10:36:06 +10:00
..
glance Include dates in detailed image output. 2012-07-31 09:15:26 +10:00
glance-api Use openstack.common.log to log request id 2012-07-13 10:58:31 -07:00
glance-cache-cleaner Don't use PasteDeploy for scrubber and cache daemons 2012-06-16 17:36:55 +01:00
glance-cache-manage Fix help messages for --debug. 2012-06-13 12:15:08 -04:00
glance-cache-prefetcher Don't use PasteDeploy for scrubber and cache daemons 2012-06-16 17:36:55 +01:00
glance-cache-pruner Don't use PasteDeploy for scrubber and cache daemons 2012-06-16 17:36:55 +01:00
glance-control Add cfg's new global CONF object 2012-06-05 21:50:55 +01:00
glance-manage Port remaining code to global conf object 2012-06-08 17:36:25 +01:00
glance-registry Use openstack.common.log to log request id 2012-07-13 10:58:31 -07:00
glance-replicator Handle images which exist but can't be seen. 2012-08-04 10:36:06 +10:00
glance-scrubber Don't use PasteDeploy for scrubber and cache daemons 2012-06-16 17:36:55 +01:00