Comment 2 for bug 1958377

One more comment. I switched to

GRUB_CMDLINE_LINUX_DEFAULT="net.ifnames=0 biosdevname=0"

as well, in order to make sure cloud-init finds the network interface after it did not work with "ens18".

However on the other Ubuntu LTS 20.04 VM I did not so this and cloud-init generates a config with "set-name: eth0" into it. I'd consider uploading the working template to the Proxmox VE instance with the non working one, but it would take a considerable amount of time using my uplink.

So I'd prefer to fix the non working one and finally understand what is going on in case cloud-init just does not apply the configuration. I had it with a Debian image that was provided to me some time ago, there it also did not apply the configuration, while on the Debian image I made, it did.