[Bug 1084028] [NEW] openvswitch based interfaces not started in time during boot

[Stefan Kooman]

Public bug reported:

If you create network interfaces (access ports) in openvswitch, and
configure them in /etc/network/interfaces, failsafe.conf will kick in
and the interfaces get configured after failsafe.conf exits. This adds
two minutes to boot time.

openvswitch config:

ovs-vsctl show
93e6b401-214b-4089-ac51-27ca43009cce
    Bridge "br0"
        Port "br0"
            Interface "br0"
                type: internal
        Port "vlan128"
            tag: 128
            Interface "vlan128"
                type: internal
        Port "bond0"
            trunks: [128]
            Interface "eth0"
            Interface "eth5"
    Bridge "br1"
        Port "bond1"
            trunks: [143, 145]
            Interface "eth1"
            Interface "eth4"
        Port "phy-br1"
            Interface "phy-br1"
        Port "br1"
            Interface "br1"
                type: internal
        Port "int-br1"
            Interface "int-br1"
    ovs_version: "1.4.3"

cat /etc/network/interfaces:

# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet manual
      pre-up ip link set $IFACE up
      post-down ip link set $IFACE down

auto eth1
iface eth1 inet manual
      pre-up ip link set $IFACE up
      post-down ip link set $IFACE down

auto eth4
iface eth4 inet manual
      pre-up ip link set $IFACE up
      post-down ip link set $IFACE down

auto eth5
iface eth5 inet manual
      pre-up ip link set $IFACE up
      post-down ip link set $IFACE down

auto vlan128
iface vlan128 inet static
    address 172.17.128.102
    netmask 255.255.255.0

I expected openvswitch (interfaces/ports/bonds/trunks) to be up-and-
running before /etc/network/interfaces gets evaluated.

Clint Byrum (Ubuntu) reported me the following:

 "failsafe.conf will exit when all interfaces marked as 'auto' are "up". The
only time you get a 2 minute delay is when it takes that long to bring those
interfaces up. Since you have these vlanXXX interfaces listed, the system
is waiting for them to come up.

It seems to me that openvswitch needs to be brought up before runlevel 2, and
so probably needs an upstart job. This sounds like a clear bug."

** Affects: openvswitch (Ubuntu)
     Importance: Undecided
         Status: New

-- 
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/1084028

Title:
  openvswitch based interfaces not started in time during boot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1084028/+subscriptions