Comment 13 for bug 1768827

Could it be that you are booting with a remote root filesystem, so with ip= set on the kernel command-line? This would usually show up as having YAML files in /run/netplan, and those can interfere with the renaming.

Otherwise, deploying systems with maas leads to network interfaces being renamed forcefully at boot, that's files in /etc/cloud/cloud.cfg.d/50-curtin-networking.conf