network intefaces for OpenVSwitch not started after boot

Bug #1814255 reported by Premysl Kouril
This bug report is a duplicate of:  Bug #1813371: OVS 2.9+ systemd integration issues. Edit Remove
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
openvswitch (Ubuntu)
New
Undecided
Unassigned

Bug Description

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

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.