Here is an example of a typical failure: http://logs.openstack.org/86/78286/2/check/check-tempest-dsvm-neutron-heat-slow/ee145bf/
Because there was a failure, the boot log of the orchestrated server is outputted (search for tempest/api/orchestration/stacks/test_neutron_resources.py:143): http://logs.openstack.org/86/78286/2/check/check-tempest-dsvm-neutron-heat-slow/ee145bf/logs/tempest.txt.gz
The timeout for this entire test is 300s, yet here the time for booting alone is 244s.
I believe this test would become significantly more reliable if the timeout was raised. 600s?
Here is an example of a typical failure: logs.openstack. org/86/ 78286/2/ check/check- tempest- dsvm-neutron- heat-slow/ ee145bf/
http://
Because there was a failure, the boot log of the orchestrated server is outputted (search for tempest/ api/orchestrati on/stacks/ test_neutron_ resources. py:143) : logs.openstack. org/86/ 78286/2/ check/check- tempest- dsvm-neutron- heat-slow/ ee145bf/ logs/tempest. txt.gz
http://
The timeout for this entire test is 300s, yet here the time for booting alone is 244s.
I believe this test would become significantly more reliable if the timeout was raised. 600s?