Comment 6 for bug 1317133

Revision history for this message
Alistair Coles (alistair-coles) wrote :

The test log link has expired so there's not sufficient information to know how to proceed with this bug. The way the test is written it is possible that container sync daemon had not completed sync updates before the test loop ran out of attempts and gave up checking.

Swift does have probe tests for container sync that are passing on a third party CI at the time of writing, for example here:

https://review.openstack.org/#/c/499634/