[Bug 2007419] Re: buildd daily kinetic, lunar, and mantic image missing systemd-resolved

[Launchpad Bug Tracker]

** Merge proposal linked:
   https://code.launchpad.net/~simpoir/livecd-rootfs/+git/livecd-rootfs/+merge/449377

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to livecd-rootfs in Ubuntu.
https://bugs.launchpad.net/bugs/2007419

Title:
  buildd daily kinetic, lunar, and mantic image missing systemd-resolved

Status in cloud-images:
  In Progress
Status in livecd-rootfs package in Ubuntu:
  Confirmed
Status in livecd-rootfs source package in Lunar:
  Confirmed

Bug description:
  [ Impact ]

   * There was a regression in the buildd images when systemd-resolved was moved
     out of systemd to a separate package, as the buildd recipes did not include
     systemd-resolved. Those images don't include a resolvconf anymore.

   * This affects buildd images only in the context where they are booted
     standalone (e.g. kvm, multipass). buildd containers which get network
     configuration injected (like launchpad) are not affected.

   * This fix adds the systemd-resolved package explicitly, making the resolver
     available on buildd images like pre-kinetic.

  [ Test Plan ]

   * Build image with project=ubuntu-base subproject=buildd
  image_target=all

   * Boot qcow2 buildd image. run `apt-get update`

   * Apt should be able to resolve mirrors and update fine.

  [ Where problems could occur ]

   * If the context in which buildd images are used injects a resolv.conf
     without unlinking the systemd-resolved stub, the resolver might revert
     the injected config to the systemd-resolved stub on restart.

  [ Original Description ]

  Hello,

  I'm trying to use the buildd daily images [1].  However, I'm having an
  issue with `systemd-resolved` not being installed on buildd's daily
  kinetic and lunar images.

  From what I can gather, systemd-resolved:
  1. exists in all other buildd daily images and buildd release images
  2. exists in the other cloud images [2]
  3. was separated from the systemd package in kinetic and lunar [3]

  It's a bit of a catch-22, because without `systemd-resolved` or
  literally `/usr/bin/resolvectl`, I can't run `apt install systemd-
  resolved` in my LXD environment.

  Can someone please advise?  Was this package excluded on purpose?

  Sources:
  [1] https://cloud-images.ubuntu.com/buildd/daily/
  [2] https://cloud-images.ubuntu.com/
  [3] https://packages.ubuntu.com/search?keywords=systemd-resolved&searchon=names&exact=1&suite=all&section=all

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/2007419/+subscriptions