Don't use hardcoded subnets in VipSubnetMap
This does not work when using custom network/subnet names in
network_data.yaml
Note: Fixed in service_net_map.j2.yaml for wallaby and before.
Change-Id: I64a4d80d0e678536170089be6e50020ff1d688a9
(cherry picked from commit ce0686a559
)
This commit is contained in:
parent
6f1aed5c7d
commit
60d9d52782
|
@ -136,8 +136,8 @@ parameters:
|
|||
{%- for network in networks if network.vip|default(false) %}
|
||||
{{network.name}}: {{network.name_lower}}_subnet
|
||||
{%- endfor %}
|
||||
redis: internal_api_subnet
|
||||
ovn_dbs: internal_api_subnet
|
||||
redis: {{ _service_nets.get('internal_api', 'ctlplane') }}_subnet
|
||||
ovn_dbs: {{ _service_nets.get('internal_api', 'ctlplane') }}_subnet
|
||||
type: json
|
||||
|
||||
# We define mappings to work around names that break when doing the
|
||||
|
|
Loading…
Reference in New Issue