Comment 1 for bug 1903993

Revision history for this message
Marios Andreou (marios-b) wrote :

looks like it is _just_ timing out... looking at https://zuul.opendev.org/t/openstack/builds?job_name=tripleo-ci-centos-8-standalone-upgrade-ussuri the success runs are all at ~ 3 hours which is the timeout

we may need to change something in the job... I don't think tempest is to blame here the tests are not taking that long https://689acbf7b1bc82ef50ab-1d2e05dc3ab5801f52a161e4cf3cffa5.ssl.cf2.rackcdn.com/762287/1/check/tripleo-ci-centos-8-standalone-upgrade-ussuri/35461a8/logs/stackviz/index.html#/testrepository.subunit/timeline?test=tempest.scenario.test_network_basic_ops.TestNetworkBasicOps.test_connectivity_between_vms_on_different_networks

We run tempest both after deployment and after upgrade. In the logs from description, the timeout happens in the tempest after upgrade.

However the tempest after deployment is only taking ~ 15 mins to run:

        * https://689acbf7b1bc82ef50ab-1d2e05dc3ab5801f52a161e4cf3cffa5.ssl.cf2.rackcdn.com/762287/1/check/tripleo-ci-centos-8-standalone-upgrade-ussuri/35461a8/job-output.txt
        * 2020-11-12 09:40:11.889457 | primary | PLAY [Validate the deployment] *************************************************
        * 2020-11-12 09:43:41.044614 | primary | TASK [os_tempest : Execute tempest tests] **************************************
2020-11-12 09:43:41.044716 | primary | Thursday 12 November 2020 09:43:41 +0000 (0:00:00.092) 0:55:18.928 *****
2020-11-12 10:02:53.300626 | primary | ok: [undercloud]