[Bug 680248] [NEW] Random VLAN subinterfacess fail to come up

Launchpad Bug Tracker 680248 at bugs.launchpad.net
Sat Feb 4 08:21:19 UTC 2012

You have been subscribed to a public bug:

Binary package hint: upstart

On machines with a fairly large number of VLAN subinterfaces (most of
our machines have ~20), a random subset of the configured subinterfaces
sometimes fail to come up on boot. Sometimes all interfaces come up
correctly, sometimes one or a few subint(s) doesn't come up. Whether any
subints fail to come up, how many subints fail, and which subints
appears completely random.

Verbose output from init(8) is attached. In this example, five subints,
bond0.47 through bond0.51, failed to come UP/RUNNING despite upstart
declaring that they entered the 'running' state:

    network-interface (bond0.47) state changed from post-start to

status(8) shows the interface in start/running, but ifconfig(8) shows
the subint isn't UP and RUNNING. For example:

    [jwm at virt03.ekgv.ca:pts/0 ~> ifconfig bond0.47
    bond0.47  Link encap:Ethernet  HWaddr e4:1f:13:7b:fa:92  
              BROADCAST MASTER MULTICAST  MTU:1500  Metric:1
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:0 
              RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B) 
    [jwm at virt03.ekgv.ca:pts/0 ~> sudo status network-interface INTERFACE=bond0.47
    network-interface (bond0.47) start/running

Subints that fail to come up are still listed in

    [jwm at virt03.ekgv.ca:pts/0 ~> fgrep bond0.47 /var/run/network/ifstate 

Representative sections of /etc/network/interfaces:

    auto bond0
    iface bond0 inet manual
        bond-slaves none

    auto eth0
    iface eth0 inet manual
        bond-master bond0
        bond-primary eth0 eth1

    auto eth1
    iface eth1 inet manual
        bond-master bond0
        bond-primary eth0 eth1

    auto bond0.47
    iface bond0.47 inet manual

    auto br10
    iface br10 inet manual
        bridge_ports bond0.47
        bridge_maxwait 0
    [more subints and bridge interfaces...]

Finally, I'm not sure it's relevant to this behavior, but I thought I'd mention it: these VLAN subinterfaces are part of bridge interfaces. All of our bridge interfaces contain only a single interface (the VLAN subint) at boot; KVM VMs are eventually added to these bridge groups.

When a VLAN subint fails to come up, so does the corresponding bridge

    [jwm at virt03.ekgv.ca:pts/0 ~> sudo status network-interface INTERFACE=br10
    status: Unknown instance: br10
    [jwm at virt03.ekgv.ca:pts/0 ~> ifconfig br10
    br10: error fetching interface information: Device not found
    [jwm at virt03.ekgv.ca:pts/0 ~> fgrep br10 /var/run/network/ifstate

** Affects: vlan (Ubuntu)
     Importance: Undecided
         Status: Fix Released

Random VLAN subinterfacess fail to come up 
You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vlan in Ubuntu.

More information about the Ubuntu-server-bugs mailing list