[Bug 2008952] Re: DNS failure while trying to fetch user-data

[Dan Bungert]

So while this bug talks about netboot, I think it isn't necessary to
involve that for testing purposes.  I suggest simply booting the desktop
daily-live with the nocloud kernel command line listed above and seeing
how things go.  Are the various network tools doing what we expect?

Note that gnome-boxes is a convenient tool for running this ISO in a VM, it seems to have a better video driver than what kvm would suggest by default. It's still possible to give it kernel command line with config like:
    <kernel>/srv/iso/lunar/vmlinuz</kernel>
    <initrd>/srv/iso/lunar/initrd</initrd>
    <cmdline>autoinstall layerfs-path=minimal.standard.live.squashfs ds=nocloud-net;s=http://boot.linuxgroove.com/ubuntu/23.04/</cmdline>

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, 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:
  Triaged
Status in netplan:
  New
Status in subiquity:
  New
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