[Bug 1988772] Re: kinetic livefs builds are failing on dns errors

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 251.4-1ubuntu4

---------------
systemd (251.4-1ubuntu4) kinetic; urgency=medium

  * debian/systemd-resolved.postinst: copy existing /etc/resolv.conf on new installs (LP: #1988772)
    Commit 20bc8a37fa ("Always setup /etc/resolv.conf on new installations.")
    added logic to copy any existing /etc/resolv.conf to
    /run/systemd/resolve/stub-resolv.conf before creating the final symlink.
    When we merged the systemd-resolved package split changes from Debian,
    this logic was not replicated, which has caused regressions.
    Move the necessary pieces from systemd.postint to systemd-resolved.postinst
    to maintain the previous /etc/resolv.conf logic.
    Files:
    - debian/systemd-resolved.postinst
    - debian/systemd.postinst
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=a34a768a929921978a67ef2192ee787255400ee5

 -- Nick Rosbrook <nick.rosbrook at canonical.com>  Tue, 06 Sep 2022
19:39:59 -0400

** Changed in: systemd (Ubuntu)
       Status: Confirmed => Fix Released

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

Title:
  kinetic livefs builds are failing on dns errors

Status in live-build package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  the livefs kinetic builds are still failing, every job failed for a
  week

  https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/kinetic/ubuntu

  >    'Temporary failure resolving 'ftpmaster.internal'

  Colin poked at it and wrote

  > livecd-rootfs initially sets up a correct /etc/resolv.conf inside its build chroot; but then
  > systemd-resolved.postinst moves that aside in favour of a symlink to /run/systemd/resolve/stub-
  > resolv.conf, but systemd-resolved itself isn't running because livecd-rootfs builds in a chroot, 
  > not a container

  he also suggested that it could be perhaps handled from live-build
  scripts/build/lb_chroot_resolv

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/live-build/+bug/1988772/+subscriptions