[Bug 482419] Re: 802.3ad interface bonding fails if started too early

[scott]

speed/duplex auto-negotiation was not the source of  the problem in my
experience (not saying that it couldn't potentially cause some problem).
Relying on auto-negotiation is not a good idea when using ether-channel.

What I found was that problem is originating from the udev (hotplug)
ethernet system which is should be loading the bonding module prior to
bringing up the bond interface.  This does not happen for some reason
and would require detailed inspection of uevents that are being
triggered when the interfaces file is parsed.

The workaround, which I posted on 5/17/11 on related bug, 574456 [
https://bugs.launchpad.net/ubuntu/+source/ifenslave-2.6/+bug/574456/comments/5
], is to use the pre-up scripts to explicitly state the _proper_ order
things should happen.  My solution works across reboots and is udev
agnostic.

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

Title:
  802.3ad interface bonding fails if started too early

Status in “ifenslave-2.6” package in Ubuntu:
  Fix Released
Status in “ifenslave-2.6” source package in Lucid:
  Triaged
Status in “ifenslave-2.6” package in Debian:
  Unknown

Bug description:
  Impact: see original report below
  How the patch fixes it: pre-up sets up master before attempting to enslave and setup slaves
  Patch: https://bugs.edge.launchpad.net/ubuntu/+source/ifenslave-2.6/+bug/482419/+attachment/1455658/+files/ifenslave-2.6-sru.diff
  Reproducing: http://ubuntuforums.org/showpost.php?p=8285696&postcount=3
  Regression potential: none known

  == Original report ==
  802.3ad bonding configurations that formerly worked on jaunty are now failing on startup under karmic. After the system has started, restarting networking will bring the bond up correctly. This only applies to bond_mode 4 / 802.3ad, I've tested that switching to bond_mode 0 corrects the issue, and other users experiencing this bug all were using bond_mode 4 as well.

  dmesg output fills with "bonding: bond0: Warning: Found an
  uninitialized port", even after the system starts up and the port
  should be "initialized"

  It appears to occur on multiple drivers (bnx2, e1000 confirmed).

  One initially wants to blame the startup ordering due to the switch to
  upstart, but I believe it is an edge case that hasn't been seen before
  because we haven't been starting up so quickly that the hardware
  hasn't had time to fully initialized.

  Configuration and output from multiple users is in this thread:
  http://ubuntuforums.org/showthread.php?p=8311572