time stestr run test_container_sync.ContainerSyncTest.test_container_synchronization {0} tempest.api.object_storage.test_container_sync.ContainerSyncTest.test_container_synchronization ... SKIPPED: Marked as unstable and skipped because of bug: https://launchpad.net/bugs/1317133, failure was: !=: reference = {'tempest-TestSyncObject-2051085311': {'bytes': 33, 'content_type': 'application/json', 'hash': '3f22a0f66f8aa0886871f5b872d7a366', 'last_modified': '2022-09-09T12:11:30.043Z', 'name': 'tempest-TestSyncObject-2051085311'}} actual = {'tempest-TestSyncObject-517842154': {'bytes': 32, 'content_type': 'application/json', 'hash': 'cdc7c879ad53c5bdb2edaa348d69fdd8', 'last_modified': '2022-09-09T12:11:30.078Z', 'name': 'tempest-TestSyncObject-517842154'}} : Different object lists in containers. ====== Totals ====== Ran: 1 tests in 604.1696 sec. - Passed: 0 - Skipped: 1 - Expected Fail: 0 - Unexpected Success: 0 - Failed: 0 Sum of execute time for each test: 604.1696 sec. ============== Worker Balance ============== - Worker 0 (1 tests) => 0:10:04.169599 real 10m14.738s user 0m1.863s sys 0m0.180s End result is speeding 10 minutes, for a skipped test.
The fix does exist in upstream (see link with ID 849801) and it is included in tags/33.0.0 meaning the bug is resolved for 17.1. Therefore I'm moving this bug to CLOSED. But we probably need to backport the fix also to 17.0 (and potentially to older releases) because of that I'm creating a clone of this bug for 17.0.
just fyi, openstack-tempest-33.0.0-1.20230406160852.1580f6f.el9ost - is part of the newest compose that passed phase2 and contains the necessary change.