Run sequentially tempest_heat 61/69961/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:00 +0000 (13:30 +0200)
commitd8da895e78040f12056b87f5fb29663a5c62881c
tree2a653c1c2b6de5bcc6d9d14043bfc63dedc1ec6b
parentfcfdac12fb36b38609246750b9f9fb3c29fd359d
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