Latest thought on this is a simple race between the S3 testcase body and S3 test teardown running near-conncurent in the Jenkins py26 and py27 builds.
A work-around using unique per-test bucket names is proposed to address the race condition:
https://review.openstack.org/#change,5590
Latest thought on this is a simple race between the S3 testcase body and S3 test teardown running near-conncurent in the Jenkins py26 and py27 builds.
A work-around using unique per-test bucket names is proposed to address the race condition:
https:/ /review. openstack. org/#change, 5590