In the cloud images, then in the ubuntu-server live images, and probably many other places too.
I'm not sure if it's cloud-init generator that should be poking netplan to "activate backend" or if netplan generator should "notice" that "we are cloud-initing, generate backend dependencies only" or some such.
Note that when this was discovered many times over, we have cargo culted shipping things like:
0 ./live- build/ubuntu- cpc/includes. chroot/ etc/systemd/ system/ network- online. target. wants/systemd- networkd- wait-online. service build/ubuntu- cpc/includes. chroot/ etc/systemd/ system/ multi-user. target. wants/systemd- networkd. service build/ubuntu- cpc/includes. chroot/ etc/systemd/ system/ sockets. target. wants/systemd- networkd. socket
0 ./live-
0 ./live-
In the cloud images, then in the ubuntu-server live images, and probably many other places too.
I'm not sure if it's cloud-init generator that should be poking netplan to "activate backend" or if netplan generator should "notice" that "we are cloud-initing, generate backend dependencies only" or some such.