Comment 0 for bug 1065077

Description: Ubuntu 12.04.1 LTS
Release: 12.04
Ifenslave-2.6 version: 1.1.0-19ubuntu5

First of all; I am not 100% sure this bug is in ifenslave-2.6, but ifenslave-2.6 is definately affected by the bug in general.

I have installed a system using PXE and preseed, which automatically partitions seperate /, /usr, /var, /tmp and swap partitions. After installing ifenslave and configuring it using the configuration example in /usr/share/doc/ifenslave-2.6/examples/two_hotplug_ethernet, I reboot the server to test if it comes up after booting.

The result is a bond0 that came up, but eth0 and eth1 haven't joined in as slaves.

In /var/log/upstart/network-interface-bond0.log, I noticed the following:

Waiting for a slave to join bond0 (will timeout after 60s)
/etc/network/if-pre-up.d/ifenslave: 240: /etc/network/if-pre-up.d/ifenslave: seq: not found
No slave joined bond0, continuing anyway
Failed to bring up bond0.

It seems that seq is not available at the time /etc/network/if-pre-up.d/ifenslave is ran. To verify, I added a 'df -h' at the top of the script, and rebooted, noticing indeed only my root filesystem is mounted when the script runs:

Filesystem Size Used Avail Use% Mounted on
/dev/mapper/rootvg-root 3.8G 631M 3.0G 18% /
udev 5.9G 260K 5.9G 1% /dev
tmpfs 2.4G 240K 2.4G 1% /run
none 5.0M 0 5.0M 0% /run/lock
Waiting for a slave to join bond0 (will timeout after 60s)
/etc/network/if-pre-up.d/ifenslave: 240: /etc/network/if-pre-up.d/ifenslave: seq: not found
No slave joined bond0, continuing anyway
Failed to bring up bond0.

Naturally, after booting is done, all filesystems are available. When running ifdown -a; ifup -a when this was the case, the bond actually does come up.

Eventually, I made a quick-fix for myself by copying /usr/bin/seq to /bin/seq, which solves the issue.

Now, I'm quite new to Ubuntu (we are figuring out if we can and want to migrate our servers from Debian to Ubuntu), and especially upstart, but from what I can see, the networking upstart script only starts on 'local-filesystems', which I assume is emited only when all filesystems are actually mounted (but here is where my knowledge pretty much ends).

If further information is needed, just let me know!