Comment 9 for bug 955527

Here's an interesting variant on the problem, that arose after many manually re-triggered Jenkins builds.

In this case the failure mode is different, in that the *first* GET on the copied image fails with 404, whereas previously the pattern was that the *second* GET on the copied would 404 after the original image had been DELETE'd.

======================================================================
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 184, in wrapped
    func(*a, **kwargs)
  File "/home/jenkins/workspace/gate-glance-python26/glance/tests/functional/test_s3.py", line 264, 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_s3.py", line 219, in _do_test_copy_from
    self.assertEqual(response.status, 200)
AssertionError: 404 != 200
>> raise self.failureException, \
          (None or '%r != %r' % (404, 200))