Comment 31 for bug 2008952

I can confirm success manually launching images via kvm in virt-manager that live desktop image builds as of 20230403 images in `/cdrom/.disk/info` have the proper systemd service ordering which places cloud-init.service `After=NetworkManager.service NetworkManager-wait-online.service`. Which allows cloud-init to resolve DNS on Ubuntu ISOs where NetworkManager is the primary network backend.

We also found a secondary bug not related to the specific NetworkManager DNS issue, once cloud-init renders initial network config to detect the datasource, it writes direct network configuration to /etc/NetworkManager/systemc-connections. If networking changes are provided in autoinstall.network, ubuntu-desktop-installer(via subiquity) writes that network config to /etc/netplan/00-installer.yaml and invokes 'netplan apply'. This results in collisions in NetworkManager configuration as netplan isn't aware of cloud-init's direct config of in /etc/NetworkManager/system-connections/cloud-init-<device>.nmconnection.

https://bugs.launchpad.net/cloud-init/+bug/2015605