Regression for previously working ifupdown configuration

[Martin Rudat]

My (currently working in 13.10) setup for ifupdown is:

auto eth0
iface eth0 inet manual
    bond-master bond0

auto bond0
iface bond0 inet dhcp
    bond-slaves none
    bond-mode 802.3ad
    bond-miimon 100

on a fresh install of trusty (as at 2014-07-23), I changed the default networking configuration to the above, and bond0 never came up. This works just fine in 13.10 with the previous version of ifenslave(-2.6), though admittedly, I've also got an eth1.

It appears that the added code ensuring that bond0 doesn't come up until at least one slave is present waits forever for ifup -a to bring up a slave interface; I assume that ifup is single-threaded, because it never attempts to bring up eth0.

I've got a workaround in place, rather than actually fixing the problem. Where the network startup script currently goes:

ifup -a

I instead have:

ifup eth0 &
ifup bond0 &

ifup -a

...and things are working for me.

I've attempted both ifup eth0 and ifup bond0, and I'm reasonably certain that, starting from a freshly booted computer, both proceeded into an infinite loop.

It's possible I'm doing it wrong, but it doesn't look like the documentation has been changed since ifenslave-2.6, so I boldly assume that a currently working configuration should continue to do so... if not, this isn't a bug with the behaviour of ifenslave, it's a bug with the un-updated documentation.

$ lsb_release -rd
Description: Ubuntu 14.04 LTS
Release: 14.04

$ apt-cache policy ifenslave
ifenslave:
  Installed: 2.4ubuntu1
  Candidate: 2.4ubuntu1
  Version table:
 *** 2.4ubuntu1 0
        500 http://mirror.internode.on.net/pub/ubuntu/ubuntu/ trusty/main amd64 Packages
        100 /var/lib/dpkg/status