From d1110c3ee84e199bb4347fd49eac6fe7891af59d Mon Sep 17 00:00:00 2001 From: Damian Dabrowski Date: Mon, 11 Jul 2022 17:05:15 +0200 Subject: [PATCH] Use network UUID for floating_network_name ``floating_network_name`` works well with UUIDs as well. This change doesn't make any difference when tempest creates public network. But when it's not, operator does not set ``tempest_public_net_name`` which leaves ``floating_network_name`` with a defeault value. In order to fix ``floating_network_name`` behavior for both scenarios, it should be set to the ``tempest_neutron_public_network_id``. We do the same thing for ``public_network_id``. Change-Id: I10e0c49b0d89b9530a523e9db79d5c7aa52359a4 --- templates/tempest.conf.j2 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/templates/tempest.conf.j2 b/templates/tempest.conf.j2 index 6dcdea4a..4fa94cba 100644 --- a/templates/tempest.conf.j2 +++ b/templates/tempest.conf.j2 @@ -103,7 +103,7 @@ build_timeout = 600 [network] endpoint_type = {{ tempest_endpoint_type }} public_network_id = {{ tempest_neutron_public_network_id }} -floating_network_name = {{ tempest_public_net_name }} +floating_network_name = {{ tempest_neutron_public_network_id }} build_timeout = 600 {% endif %}