Public bug reported: After upgrade to vivid, my system takes nearly 4 minutes to boot. This appears to be related to the new systemd unit ordering.
[Unit] Description=Open vSwitch After=network.target openvswitch-nonetwork.service ... root@mystic:/lib/systemd/system# systemd-analyze blame | head 2min 233ms ifup-wait-all-auto.service ... Open vSwitch is being started after the network, but the network needs Open vSwitch to start since my host traffic is flowing through the bridge: root@mystic:/lib/systemd/system# ovs-vsctl show 838a8aa4-4811-447d-8dcc-dbb675b78968 Bridge "br0" Port "br0" tag: 1 Interface "br0" type: internal Port "vlan121" tag: 121 Interface "vlan121" type: internal Port "eth0" tag: 1 Interface "eth0" ovs_version: "2.3.1" The interfaces do eventually start correctly, but only after the long timeout above. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: openvswitch-switch 2.3.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Fri Apr 24 14:10:19 2015 EcryptfsInUse: Yes ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: openvswitch UpgradeStatus: Upgraded to vivid on 2015-04-24 (0 days ago) ** Affects: openvswitch (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1448254 Title: openvswitch systemd unit file ordering wrong To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1448254/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs