@tom-verdaat I'm temporarily removing this as dup, because I can't reproduce your error on xenial, or maybe I don't understand the specific error you're talking about.
> # ifup bond1 > Waiting for a slave to join bond1 (will timeout after 60s) This isn't new; trying to do this even with an edited if-pre-up.d/vlan script (to remove the ifup for the vlan raw device) still hangs. I believe trying to do this has always hung (waited until timeout). Were you able to do this (without the bond waiting 60s for a slave, but never getting one)? If so, what version of ifupdown and vlan are you using? > # ifup eno1 > Waiting for bond master bond1 to be ready ... > # ip link | grep -E 'eno[1|2]|bond1*' > eno1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond1 > state UP mode > DEFAULT group default qlen 1000 > eno2: <BROADCAST,MULTICAST> mtu 1500 qdisc mq state DOWN mode DEFAULT group > default qlen 1000 > bond1: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state > UP mode DEFAULT > group default qlen 1000 This is also completely normal, you're bringing up only eno1; there should be no expectation that eno2 will also get brought up. It's a quirk of ifupdown that bond1 is also created and brought up as eno1's bond master. Has it ever worked differently for you? If so, what version of ifupdown and vlan? Or, if you mean that this is hanging - I can't reproduce that; is that what you mean? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759573 Title: vlan on top of untagged network won't start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1759573/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
