In the TestCopyToFile._do_test_copy_from() method, there is some faulty logic it seems:
# DELETE original image
path = "http://%s:%d/v1/images/%s" % ("0.0.0.0", self.api_port,
original_image_id)
http = httplib2.Http()
response, content = http.request(path, 'DELETE')
self.assertEqual(response.status, 200)
# GET image again to make sure the existence of the original
# image in from_store is not depended on
path = "http://%s:%d/v1/images/%s" % ("0.0.0.0", self.api_port,
copy_image_id)
http = httplib2.Http()
response, content = http.request(path, 'GET')
self.assertEqual(response.status, 200)
The problem is that the deletion path for the original image is not correct. It needs to be a DELETE call against the Swift or S3 remote backend image, not the local Glance server.
This causes the following failure:
FAIL: Ensure we can copy from an external image in S3.
----------------------------------------------------------------------
Traceback (most recent call last):
File "/home/jenkins/workspace/gate-glance-python26/glance/tests/utils.py", line 166, in _runner
func(*args, **kw)
File "/home/jenkins/workspace/gate-glance-python26/glance/tests/utils.py", line 184, in wrapped
func(*a, **kwargs)
File "/home/jenkins/workspace/gate-glance-python26/glance/tests/functional/test_swift.py", line 542, in test_copy_from_s3
self._do_test_copy_from('s3', get_s3_uri)
File "/home/jenkins/workspace/gate-glance-python26/glance/tests/functional/test_swift.py", line 511, in _do_test_copy_from
self.assertEqual(response.status, 200)
AssertionError: 404 != 200
>> raise self.failureException, \
(None or '%r != %r' % (404, 200))
The point of that delete in the test is to ensure that the copied image (in swift) is independent of the original image (in s3).
Now I think it should be OK for the deletion of the *original* image to be mediated by the glance API layer, to avoid the test being directly boto-aware.
But the fact that the subsequent GET of the copied image ID fails with a 404 indicates either:
(a) the copy isn't really independent of the existence of the original,
or:
(b) swift is intermittently broken.
Evidence pointing to option (b) includes the fact that the mysterious 404 returned by swift afflicts other tests intermittently, e.g TestS3.
I'll continue to dig tomorrow, but I suspect an intermittent swift issue may be the nub of the problem.