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

[Dan Bungert]

> So I wonder what is the exact sequence of events for running the
Netplan generator (by systemd), installing the 50-cloud-init.yaml file
(by cloud-init), installing the 01-network-manager-all.yaml file (by the
installer?), executing `netplan apply` (by cloud-init).

By the time Subiquity has started, the bad interaction has already taken place.
In this nocloud case, cloud-init should have been able to retrieve the user-data and other things, that failed.  So at Subiquity start time, we ask for the autoinstall and get an empty answer.  An empty answer is quite common - that is what happens in a normal interactive install - so it's not immediately obvious that a misbehavior has taken place.

-- 
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