Comment 6 for bug 1888726

@Dan

Just ran into this issue in curtin's vmtest for network_vlan on groovy. I can confirm that if the netplan config includes the driver match on the physical interfaces, then the vlans come up just fine.

I was thinking that netplan could inject the driver of the underlying device into the match section. That would help in these situations, however, I know of a few scenarios where this would need to be disabled (On Azure, for example, their Advanced Networking which auto-bonds an SRIOV interface and a HyperV nic together as eth0).

Also, this scenario does *NOT* fail for me on Focal, so I'm wondering what changed between either netplan or systemd?

Focal:
netplan.io 0.99-0ubuntu3~20.04.2
systemd 245.4-4ubuntu3.2

Groovy
netplan.io 0.99-0ubuntu6
systemd 246-2ubuntu1