Sorry, correction. It results in two `name: br-NAME` bridges defined on after the other in `/etc/os-net-config/config.yaml`, not in OvS. The problem is that the second one doesn't get created in OvS.
So this output is from my config.yaml file: ``` - type: ovs_bridge name: br-tenant mtu: 9000 dns_servers: ['8.8.8.8'] use_dhcp: false addresses: - ip_netmask: 172.16.0.120/24 routes: [] members: - type: interface name: nic5 mtu: 9000 use_dhcp: false primary: true - type: ovs_bridge name: br-ex mtu: 9000 dns_servers: ['8.8.8.8'] use_dhcp: false addresses: - ip_netmask: 172.20.10.23/16 routes: [{'default': True, 'next_hop': '172.20.0.254'}] ```
Sorry, correction. It results in two `name: br-NAME` bridges defined on after the other in `/etc/os- net-config/ config. yaml`, not in OvS. The problem is that the second one doesn't get created in OvS.
So this output is from my config.yaml file: 16.0.120/ 24 20.10.23/ 16
```
- type: ovs_bridge
name: br-tenant
mtu: 9000
dns_servers: ['8.8.8.8']
use_dhcp: false
addresses:
- ip_netmask:
172.
routes: []
members:
- type: interface
name: nic5
mtu: 9000
use_dhcp: false
primary: true
- type: ovs_bridge
name: br-ex
mtu: 9000
dns_servers: ['8.8.8.8']
use_dhcp: false
addresses:
- ip_netmask:
172.
routes: [{'default': True, 'next_hop': '172.20.0.254'}]
```