In case it help others - I had the same root cause issue with a slightly different setup. I was using link files placed at /etc/systemd/network to rename my adapters, and it caused the same problem. For example, I had /etc/systemd/network/10-en_public.link with contents like:
[Match] MACAddress=xx:xx:xx:xx:xx:xx [Link] Name=en_public And this would cause the same issue as the udev rule renaming method. I'd get the same error message "Wait for Network to be Configured was skipped..." for the same reason, though in my scenario, I'm not sure the generator file was ever created. Switching to use the netplan match like suggested, including the set-name property, fixed the problem and kept my adapters with the desired names. Note that the id used as the key in the ethernets dict in the yaml is not used to set the interface name and does not have to match the original interface name when you use the match property. Instead, you can just set the key to something unique (e.g. "my_adapter_id_0" and then use set-name to actually set the adapter name. The key will just be used for the link/network files created at /run/systemd/network. See https://netplan.readthedocs.io/en/latest/netplan-yaml/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063973 Title: network-online.target is reached before netplan-configured interfaces are online To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2063973/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
