Actually, title should be "juju bootstrap fails with only bonding interface".
Anyhow, steps to reproduce are: - stop bond0 - stop udev - try ifup .. eth0 eth1 bond0 Ifup ends up stuck. udev _should_ trigger bringing of other devices, but when ifup is called from add-juju-bridge, it does not work as advertised. Could it be that, because interfaces file is moved, and new one is created, with different content, that udev just get's confused? H. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1590052 Title: juju deploy brings up interfaces in wrong order To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju/+bug/1590052/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
