yahoo-eng-team team mailing list archive

[Chad Smith <2008952@xxxxxxxxxxxxxxxxxx>]

Closing the cloud-init task here as invalid because we have livecd-
rootfs overlay config files allow for cloud-init.service to get ordered
After=NetworkManager.service which solves the immediate DNS issues in
early boot. Long-term cloud-init will need to spec out options to prefer
ordering after NetworkManager versus systemd-networkd at systemd
generator timeframe because ordering After=NetworkManager is
incompatible with cloud-init's default Before=sysinit.target.

We'll take that long-term work as a separate bug for cloud-init
https://bugs.launchpad.net/cloud-init/+bug/2015949 to discern how best
to position upstream cloud-init.service files to cope with service
ordering conflicts to prefer NetworkManager.service over systemd-
networkd.


** Changed in: cloud-init
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/2008952

Title:
  DNS failure while trying to fetch user-data

Status in cloud-init:
  Fix Released
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