YES! --- root@provisioned:~# pstree -a ... ├─ifup --allow auto eth2 │ └─sh -c run-parts /etc/network/if-pre-up.d │ └─run-parts /etc/network/if-pre-up.d │ └─ifenslave /etc/network/if-pre-up.d/ifenslave │ └─sleep 0.1 ---
One slave interface, eth2 in this case, got the ifupdown lock and is running an infite loop waiting for the master bonding interface which will never run without the lock. Resuming: So bonding had to have both networking scripts running (network- interface and networking) to work AND having both scripts running would case race conditions sometime. Disabling one of the scripts would also cause race condition if right triggers are set (like i showed in this example). Fixing ifupdown race conditions led me to realize ifenslave is taking wrong decisions and can cause deadlocks. Ifenslave must be fixed together... * wait for next comments. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1337873 Title: Precise, Trusty, Utopic - ifupdown initialization problems caused by race condition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1337873/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
