> Why would bond0 get created when loading the bonding module? Because the default module parameter max_bonds for bonding module is 1, meaning create one bond upon bond module loading.
I have since hit similar issue with networkd where bonding module would be autoprobed, bond0 created, and confuse networkd (bond0 already exists, not touching it). I have since applied max_bonds=0 and used networkd. I guess I can try this again with ifupdown, max_bond=0, and check what sort of udev events are received. Imho we should default to max_bonds=0 such that loading bonding module doesn't create stray interfaces. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1636708 Title: ifup -a does not start dependants last, causes deadlocks with vlans/bonding To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1636708/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
