Thanks a lot for your work, Dan! Unfortunately, I wasn't able to pick up the new bug from here, sorry for that. (It appears I did not get any notification on your comments, need to check that)
The bridges are managed by OpenStack Neutron from Ubuntu cloud archives and with names derived from the network UUID in the cluster database. It might work for a very limited set of bridges, if they do not set different options. AFAIK, OpenStack Neutron is still working on supporting using external bridges (https://bugs.launchpad.net/neutron/+bug/1105488).
As we have bridges on VLANs on bonded interfaces (currently managed with systemd-networkd), I will see if I have to replace that all or if there is an option to just have systemd-networkd not set nomaster...
Thanks a lot for your work, Dan! Unfortunately, I wasn't able to pick up the new bug from here, sorry for that. (It appears I did not get any notification on your comments, need to check that)
The bridges are managed by OpenStack Neutron from Ubuntu cloud archives and with names derived from the network UUID in the cluster database. It might work for a very limited set of bridges, if they do not set different options. AFAIK, OpenStack Neutron is still working on supporting using external bridges (https:/ /bugs.launchpad .net/neutron/ +bug/1105488).
As we have bridges on VLANs on bonded interfaces (currently managed with systemd-networkd), I will see if I have to replace that all or if there is an option to just have systemd-networkd not set nomaster...
Thanks!