master promotion blocker
During both openstack-periodic-master runs today at [1][2] the periodic-tripleo-ci-centos-7-standalone-full-tempest-master fails during the tempest.api.compute.images tests specifically test_delete_saving_image with trace like:
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/tempest/api/compute/images/test_images.py", line 55, in test_delete_saving_image
wait_until='SAVING')
File "/usr/lib/python2.7/site-packages/tempest/api/compute/base.py", line 346, in create_image_from_server
waiters.wait_for_image_status(client, image_id, wait_until)
File "/usr/lib/python2.7/site-packages/tempest/common/waiters.py", line 181, in wait_for_image_status
raise lib_exc.TimeoutException(message)
tempest.lib.exceptions.TimeoutException: Request timed out
Details: (ImagesTestJSON:test_delete_saving_image) Image a507b352-0c86-4b3e-b614-45cff4eaaa46 failed to reach SAVING state (current state ACTIVE) within the required time (300 s).
[1] http://logs.rdoproject.org/openstack-periodic-master/opendev.org/openstack/tripleo-ci/master/periodic-tripleo-ci-centos-7-standalone-full-tempest-master/85662f6/logs/stestr_results.html
[2] http://logs.rdoproject.org/openstack-periodic-master/opendev.org/openstack/tripleo-ci/master/periodic-tripleo-ci-centos-7-standalone-full-tempest-master/35fea03/logs/stestr_results.html
Looks like a repeat of https:/ /bugs.launchpad .net/tempest/ +bug/1713163; see comment 5 for suggestion on updating the tempest test's definition of success. Basically, don't require observing the transitional SAVING state.