Public bug reported:
Boot order of openvswitch and ifupdown scripts to bring up interface
definitions specified for OVS in /etc/network/interfaces are wrong
again. The ifupdown scripts try to bring up ovs interfaces before OVS is
actually running which results in failure and the interfaces defined in
/etc/network/interfaces are not up after machine boot.
The ordering in openvswitch systemd unit files is wrong and for some
reasons the unit file openvswitch-nonetwork.service unit was removed
from Bionic without appropriate substitute. We have currently fixed it
by modifying openvswitch-switch.service ovs-vswitchd.service and ovsdb-
server.service units by moving network-pre.target from After to Before
clause.
Thanks,
Prema
** Affects: openvswitch (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1814255
Title:
network intefaces for OpenVSwitch not started after boot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1814255/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
