The fixes in vlan package are insufficient, as networking.service spawns [email protected] in parallel with no ordering information and therefore systemd is free to process them in a racy manner. At boot [email protected] are racing with networking.service and can result in a deadlock as you have experienced.
@tom-verdaat To resolve boot time races, you need to provide manual dependency ordering of the [email protected] systemd units, as at the moment, unfortunately, these are not automatically generated. For you pasted config I believe you require the following files: # cat /etc/systemd/system/[email protected]/order.conf [Unit] [email protected] [email protected] # cat /etc/systemd/system/[email protected]/order.conf [Unit] [email protected] [email protected] [email protected] [email protected] In 17.10 and later releases these races are fixed with netplan. netplan is also available and can be used on xenial. netplan generates correct configuration and then all of bonds/vlans are managed by networkd in a race-free manner. I apologize for the inconvenience =( -- 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
