Use network UUID for floating_network_name

Code Issues Proposed changes

``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

This commit is contained in:

Damian Dabrowski

2022年07月11日 17:05:15 +02:00

committed by Damian Dąbrowski

parent 514b0ca612

commit d1110c3ee8

1 changed files with 1 additions and 1 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

2
templates/tempest.conf.j2

View File

@@ -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 %}

Use network UUID for floating_network_name

2 templates/tempest.conf.j2 Unescape Escape View File

2
templates/tempest.conf.j2

View File