One of the things triggering this misbehavior is that glanceclient is not sending the request's content-lenght and therefore, Glance doesn't know the image/request size when the call to the store is made.
Unfortunately, there's a bit more to this issue since this doesn't happen deterministically. There seems to be a race in the swift driver that's causing the first conflict error, which then makes the subsequent requests fail.
One of the things triggering this misbehavior is that glanceclient is not sending the request's content-lenght and therefore, Glance doesn't know the image/request size when the call to the store is made.
Unfortunately, there's a bit more to this issue since this doesn't happen deterministically. There seems to be a race in the swift driver that's causing the first conflict error, which then makes the subsequent requests fail.