Ubuntu
live-build package

kinetic livefs builds are failing on dns errors

Bug #1988772 reported by Sebastien Bacher
42
This bug affects 6 people
Affects Status Importance Assigned to Milestone
live-build (Ubuntu)
Invalid
Undecided
Unassigned
systemd (Ubuntu)
Fix Released
Critical
Unassigned

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

Tags: fr-2661

Related branches

~enr0n/ubuntu/+source/systemd:ubuntu-kinetic
Steve Langasek: Approve
Diff: 65 lines (+20/-12)
3 files modified
debian/changelog (+17/-0)
debian/systemd-resolved.postinst (+3/-1)
debian/systemd.postinst (+0/-11)
Łukasz Zemczak (sil2100)
tags: added: fr-2661
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in live-build (Ubuntu):
status: New → Confirmed
Revision history for this message
Steve Langasek (vorlon) wrote :

If the systemd-resolved postinst doesn't work correctly in a chroot, I think the problem needs to be fixed there, not worked around in the live build system

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in systemd (Ubuntu):
status: New → Confirmed
Łukasz Zemczak (sil2100)
Changed in systemd (Ubuntu):
importance: Undecided → Critical
Revision history for this message
Launchpad Janitor (janitor) wrote :

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 <email address hidden> Tue, 06 Sep 2022 19:39:59 -0400

Changed in systemd (Ubuntu):
status: Confirmed → Fix Released
Matthieu Clemenceau (mclemenceau)
tags: added: foundations-todo
Revision history for this message
Steve Langasek (vorlon) wrote :

Images building successfully now.

Changed in live-build (Ubuntu):
status: Confirmed → Invalid
Brian Murray (brian-murray)
tags: removed: foundations-todo
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.