Comment 18 for bug 1802004

I cannot seem to reproduce this in a Ubuntu Jammy 22.04 LXD VM. I wonder if this is still an issue on more recent versions of Ubuntu (systemd/netplan)?

$ cat /etc/netplan/50-cloud-init.yaml
network:
    version: 2
    ethernets:
        lan0:
            match:
                macaddress: "00:16:3e:dd:53:87"
            set-name: lan0
            dhcp4: no
            addresses: [10.238.94.250/24]
            gateway4: 10.238.94.1

Rename seems to work as expected and the interface is up, with IP address assigned.
$ journalctl | grep rename
Oct 27 13:15:16 test kernel: virtio_net virtio10 lan0: renamed from enp5s0
Oct 27 13:15:16 test systemd-networkd[336]: enp5s0: Interface name change detected, renamed to lan0.
Oct 27 13:15:36 test kernel: virtio_net virtio10 lan0: renamed from eth0

$ networkctl
IDX LINK TYPE OPERATIONAL SETUP
  1 lo loopback carrier unmanaged
  2 lan0 ether routable configured

$ ip addr show lan0
2: lan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 00:16:3e:dd:53:87 brd ff:ff:ff:ff:ff:ff
    inet 10.238.94.250/24 brd 10.238.94.255 scope global lan0
       valid_lft forever preferred_lft forever
    inet6 fd42:7213:f20e:bd74:216:3eff:fedd:5387/64 scope global dynamic mngtmpaddr noprefixroute
       valid_lft 3309sec preferred_lft 3309sec
    inet6 fe80::216:3eff:fedd:5387/64 scope link
       valid_lft forever preferred_lft forever