[Bug 660974] Re: net-device-up emitted for bonding members

[Stéphane Graber]

I was going to merge your patch but just remembered I actually fixed
this in a different way :)

Here's roughly what happens when eth0 appears (bond member):
 - upstart receives net-device-added INTERFACE=eth0
 - network-interface is triggered
 - ifup --allow auto eth0 is called
 - pre-up script for eth0 notices bond0 doesn't exist, creates it and wait for it to be ready
 - upstart receives net-device-added INTERFACE=bond0
 - network-interface is triggered
 - ifup --allow auto bond0 is called
 - pre-up script for bond0 initialises the bond and joins eth0 to it
 - net-device-up is emitted for IFACE=bond0
 - the pre-up script for eth0 continues
 - net-device-up is emitted for IFACE=eth0

So basically net-device-up IFACE=eth0 now will only get emitted once
bond0 is online, configured and has eth0 as a slave.

** Changed in: ifupdown (Ubuntu)
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/660974

Title:
  net-device-up emitted for bonding members

Status in “ifupdown” package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: ifupdown

  net-device-up is emitted when bonding link members are configured,
  which is rather misleading as the machine won't get connectivity until
  the master device is configured. This leads to problems if you for
  example wants to use a post-up hook in /etc/network/interfaces to wait
  for your less cooperative switch that takes 60 seconds to establish a
  LACP trunk.

  The attached patch fixes the issue.

  # lsb_release -rd
  Description:    Ubuntu 10.04.1 LTS
  Release:        10.04

  # apt-cache policy ifupdown
  ifupdown:
    Installed: 0.6.8ubuntu29.1
    Candidate: 0.6.8ubuntu29.1

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