After a reboot I see the following:
$ ls /run/network/
ifenslave.bond0 ifstate ifup.eth0 ifup.eth1 ifup.eth2 ifup.lo
This causes 'ifdown bond0' to fail. If we workaround it by doing:
$ sudo touch /run/network/ifup.bond0
$ echo 'bond0=bond0' | sudo tee /run/network/ifstate
We can run this now:
$ sudo ifdown bond0
RTNETLINK answers: No such process
And ip addr shows eth1/eth2 down and bond0 not present at all.
This makes me suspect that the files in /run/network aren't being
created properly in the ifup -a case when we have a bond.
** Changed in: ifenslave (Ubuntu)
Assignee: (unassigned) => Chris J Arges (arges)
** Changed in: ifenslave (Ubuntu)
Importance: Undecided => High
** Changed in: ifenslave (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1254120
Title:
Bonded interfaces don't come down with a ifdown -a
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifenslave/+bug/1254120/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
