Hi list!

Recently we discovered that OVS bridges on Debian were no longer
created at boot time, after upgrading from Buster to Bullseye.

We had config like:

 allow-ovs vmbr2
 iface vmbr2 inet manual
       ovs_type OVSBridge
        ...

As per the documentation in https://github.com/openvswitch/ovs/blob/master/debian/openvswitch-switch.README.Debian

On Bullseye, this no longer works, and you have to use

 auto vmbr2

to get the interfaces to start at boot time, even though the above
readme file warns not to do that. Someone else even filed a Debian
bug about this[1], where the suggestion was made to use "auto"
instead of "allow-ovs".

After digging around we found the reason, which is that on Buster
the ifupdown script starts the /etc/init.d/openvswitch-switch init script,
which in turn does "ifup --allow ovs", but on Bullseye the
openvswitch-switch.service no longer starts that init script, but requires
ovsdb-server.service and ovs-vswitchd.service instead.

As far as I can see, neither of these services actually call ifup to bring
up any interfaces.

So, essentially my question is simple: what is the recommended way to get
ovs interfaces started on Debian bullseye?

Best regards and thanks in advance,

Roel

 [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989720

_______________________________________________
discuss mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Reply via email to