[Bug 1078387] Re: bonded interface doesn't reliably come up after reboot

[Mark Fox]

Compared the relevant configuration files between the server with the
issue and the one that works. Except for IP address, the files are
identical.

The only two differences between the machines is that the one that works
has the default layout for partitions as set up by the Ubuntu installer
(using LVM). The problem machine has additional LVM volumes for /var,
/tmp, /home, and /usr. My guess is that /usr is the issue. I've broken
out everything but /usr on the machine I need for production and it
works fine. I'll set up the other machine similarly and try putting /usr
on a separate partition to see if that causes anything funny.

The other difference is that I set some of the options for bonding
(mode=802.3ad miimon=100 xmit_hash_policy=layer3+4) in /etc/modules.
I've played with adding and removing those options and it doesn't seem
to make a difference. Bonding comes up reliably either way.

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

Title:
  bonded interface doesn't reliably come up after reboot

Status in “ifenslave-2.6” package in Ubuntu:
  New

Bug description:
  Ubuntu 12.04 LTS (release 12.04 according to lsb_release -rd). Machine
  has four NICs.

  Set up a four-interface bond using the method outlined at
  http://www.stgraber.org/2012/01/04/networking-in-ubuntu-12-04-lts/.
  Restarting networking shows everything working as one would expect.
  Testing shows performance and behaviour to be what you would expect of
  a bonded interface.

  After a reboot things get interesting: Sometimes none of the slave
  interfaces come up and the bond therefore fails. Sometimes one or two
  of the interfaces come up, along with the bond. Leaving the machine
  for 15 minutes or so does not make for any changes. The interfaces
  that didn't come up at boot remain down. Unplugging, then replugging,
  cables makes no difference either. Restarting networking gets things
  back in their proper state.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifenslave-2.6/+bug/1078387/+subscriptions