Is it possible this regressed sometime between Bionic and Focal? I am
observing this in 20.04. Early in dmesg I see my interface renamed from
eth1 to eno2, then my netplan attempts to rename with a match (on
name=eno2) to my desired name ("ceph" in this case). I see syslog
message:systemd-udevd[844]: eno2: Config file /run/systemd/network/10-netplan- eno2.link matches device based on renamed interface name, ignoring but after boot and login, netplan apply is succsesful. Steps in #11 do not work, even though I verify the link file is in the new initrd.img at usr/lib/systemd/network/10-netplan-eno2.link What _did_ work for me, is editing this file first to refer to the eth1 name instead of eno2 (the file was written, I believe, by netplan). After this I can change my netplan to refer to the desired name with no set-name rule. Obvs. I can cut out some steps as I replicate this solution to the other servers. To summarize: write out /etc/systemd/network/10-netplan-eno2.link in a way that refers to eth1 (instead of eno2) and sets ultimately desired name. update-initramfs. netplan uses desired name without rename rules. I suppose I can/should rename that file to 10-netplan-ceph.link :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1770082 Title: systemd-networkd not renaming devices on boot To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1770082/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
