It appears we have the following *ordering* relationship between
systemd-resolved.service, cloud-init.service, network.target, and
network-online.target:
network-online.target
/.................... \
/...................... \
/.........................\
network.target cloud-init.service
/
/
/
systemd-resolved.service
See attached graph for more details. This is consistent with the
timeline shown in comment #13.
Since cloud-init.service apparently requires DNS, I would simply try to
add `After=systemd-resolved.service` to `cloud-init.service`.
** Attachment added: "systemd-analyze-dot.svg"
https://bugs.launchpad.net/cloud-init/+bug/2008952/+attachment/5654458/+files/systemd-analyze-dot.svg
--
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:
Triaged
Status in netplan:
Invalid
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
--
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
