Run sequentially tempest_heat 60/69960/1
authorCédric Ollivier <cedric.ollivier@orange.com>
Sun, 19 Apr 2020 10:48:33 +0000 (12:48 +0200)
committerCédric Ollivier <cedric.ollivier@orange.com>
Sun, 19 Apr 2020 11:29:18 +0000 (13:29 +0200)
commitc2e3d911d9eaf987d18b3b895778c411e62efc4a
tree09a4c1fe0c791b0bf8c1b72da29d840446fecde5
parent0c296f207e82b9253235ff86c25dc2223a495c9a
Run sequentially tempest_heat

It's forced by design else it remains a few resources.
It also sets fixed_subnet_name and network_for_ssh to avoid falsy
discovery as it seems [1]

[1] http://artifacts.opnfv.org/functest/X5GDYF3B0R2B/functest-opnfv-functest-smoke-jerma-tempest_heat-run-18/tempest_heat/tempest-report.html

Change-Id: Ieb584ddc1c0b4ebb543e9d69277a20aaee0fbac0
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
docker/smoke/testcases.yaml
functest/ci/testcases.yaml
functest/opnfv_tests/openstack/tempest/tempest.py