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 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2008952 Title: DNS failure while trying to fetch user-data Status in cloud-init: In Progress Status in netplan: Invalid Status in subiquity: New Status in livecd-rootfs package in Ubuntu: Fix Released Status in systemd package in Ubuntu: New Bug description: In testing netboot + autoinstall of the new ubuntu desktop subiquity based installer for 23.04 I found cloud-init is failing to retrieve user-data because it can't resolved the hostname in the URL. This same configuration does work for 22.04 based subiquity, so seems a regression. From the ipxe config: imgargs vmlinuz initrd=initrd \ ip=dhcp \ iso-url=http://cdimage.ubuntu.com/daily-live/pending/lunar-desktop-amd64.iso \ fsck.mode=skip \ layerfs-path=minimal.standard.live.squashfs \ autoinstall \ 'ds=nocloud-net;s=http://boot.linuxgroove.com/ubuntu/23.04/' \ That fails, but if we replace boot.linuxgroove.com with the IP it works. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/2008952/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
