Run sequentially tempest_heat 63/69963/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:30:34 +0000 (13:30 +0200)
commitacc21264c88ed92145fe8f247b22dd0fbcacc321
tree4843ad6cc16a9f5bf60b63d6d6d2320dd78e89c0
parent086f7e96ed17fa065db4d1b757ecc7768c7615be
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>
(cherry picked from commit c2e3d911d9eaf987d18b3b895778c411e62efc4a)
docker/smoke/testcases.yaml
functest/ci/testcases.yaml
functest/opnfv_tests/openstack/tempest/tempest.py