Bug #2047975 “package systemd-resolved 253.5-1ubuntu7 failed to ...” : Noble (24.04) : Bugs : systemd package : Ubuntu

Revision history for this message

CloudRoot AB (cloudrootab) wrote on 2024-01-03:

#1

AptOrdering.txt Edit (24.9 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (2.9 KiB, text/plain; charset="utf-8")
Df.txt Edit (941 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (152.3 KiB, text/plain; charset="utf-8")
DpkgHistoryLog.txt Edit (80.3 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (106.2 KiB, text/plain; charset="utf-8")
DuplicateSignature.txt Edit (423 bytes, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (1.2 KiB, text/plain; charset="utf-8")
modified.conffile..etc.systemd.resolved.conf.txt Edit (1.4 KiB, text/plain; charset="utf-8")

Ubuntu Foundations Team Bug Bot (crichton) on 2024-01-04

affects:

ubuntu → systemd (Ubuntu)

Apport retracing service (apport) on 2024-01-22

tags:

removed: need-duplicate-check

Revision history for this message

Launchpad Janitor (janitor) wrote on 2024-04-12:

#2

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

Changed in systemd (Ubuntu):
status:	New → Confirmed

Daniel van Vugt (vanvugt) on 2024-04-26

summary:	package systemd-resolved 253.5-1ubuntu7 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess - returned error exit status 1 + returned error exit status 1 [cp: '/etc/resolv.conf' and + '/run/systemd/resolve/stub-resolv.conf' are the same file]
tags:	added: mantic

Revision history for this message

Nick Rosbrook (enr0n) wrote on 2024-04-29 (last edit on 2024-04-29):

#3

I got some information from a user on a more recent duplicate (bug 2063533). The problem seems to be that some users, when disabling the stub-resolver, also create a symlink /etc/resolv.conf -> /run/systemd/resolve/resolv.conf. This is not actually necessary because systemd-resolved will make stub-resolv.conf a symlink to resolv.conf when DNSStubListener=no.

Hence, the command

cp "${DPKG_ROOT}/etc/resolv.conf" "${DPKG_ROOT}/run/systemd/resolve/stub-resolv.conf"

in systemd-resolved.postinst fails because the source and destination are *both* symlinks to /run/systemd/resolve/resolv.conf.

Changed in systemd (Ubuntu Noble):
status:	New → Triaged
importance:	Undecided → High
assignee:	nobody → Nick Rosbrook (enr0n)
tags:	added: foundations-todo systemd-sru-next

Nick Rosbrook (enr0n) on 2024-04-30

tags:

removed: foundations-todo

Nick Rosbrook (enr0n) on 2024-05-17

Changed in systemd (Ubuntu):
status:	Confirmed → Fix Committed

Nick Rosbrook (enr0n) on 2024-05-17

description:

updated

Nick Rosbrook (enr0n) on 2024-05-17

description:	updated
description:	updated

Nick Rosbrook (enr0n) on 2024-05-17

Changed in systemd (Ubuntu Noble):
status:	Triaged → In Progress

Revision history for this message

Marco Trevisan (Treviño) (3v1n0) wrote on 2024-05-20 (last edit on 2024-05-21):

#4

This is related to https://askubuntu.com/questions/1510951/do-release-upgrade-from-22-04-to-24-04-deleted-systemd-resolved right?

Since I manually upgraded a machine and after the upgrade:
- systemd-resolved wasn't there
- resolvconf was still installed
- no domain resolution was working

Once I manually installed systemd-resolved, all the above were fixed.

EDIT: Fixed link

Revision history for this message

Nick Rosbrook (enr0n) wrote on 2024-05-21:

#5

> This is related to https://discourse.ubuntu.com/t/ubuntu-desktop-s-24-10-dev-cycle-the-roadmap/45120 right?

I don't see how this is related.

> Once I manually installed systemd-resolved, all the above were fixed.

This bug is not about systemd-resolved not getting installed on upgrades (that is bug 2063464).

Revision history for this message

Marco Trevisan (Treviño) (3v1n0) wrote on 2024-05-21:

#6

Sorry I put the wrong link even on editing...

I meant https://askubuntu.com/questions/1510951/do-release-upgrade-from-22-04-to-24-04-deleted-systemd-resolved but as you noted is definitely lp:2063464 which I still noticed since I went through dist-upgrade manually.

Revision history for this message

Łukasz Zemczak (sil2100) wrote on 2024-05-22: Please test proposed package

#7

Hello CloudRoot, or anyone else affected,

Accepted systemd into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/255.4-1ubuntu8.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-noble. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Changed in systemd (Ubuntu Noble):
status:	In Progress → Fix Committed
tags:	added: verification-needed verification-needed-noble

Revision history for this message

Nick Rosbrook (enr0n) wrote on 2024-05-22:

#8

Download full text (6.0 KiB)

I have verified the fix using 255.4-1ubuntu8.1 from noble-proposed. I created a LXD jammy container:

root@j:~# cat /etc/os-release
PRETTY_NAME="Ubuntu 22.04.4 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.4 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=jammy

And then disabled the stub-resolver according to the test plan:

root@j:~# mkdir -p /etc/systemd/resolved.conf.d/
root@j:~# cat > /etc/systemd/resolved.conf.d/no-stub-resolver.conf << EOF
[Resolve]
DNSStubListener=no
EOF
root@j:~# ln -sf /run/systemd/resolve/resolv.conf /etc/resolv.conf
root@j:~# systemctl restart systemd-resolved
root@j:~# systemctl status systemd-resolved
● systemd-resolved.service - Network Name Resolution
     Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled)
     Active: active (running) since Wed 2024-05-22 15:10:08 UTC; 19s ago
       Docs: man:systemd-resolved.service(8)
             man:org.freedesktop.resolve1(5)
             https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
             https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients
   Main PID: 1079 (systemd-resolve)
     Status: "Processing requests..."
      Tasks: 1 (limit: 18947)
     Memory: 4.5M
        CPU: 57ms
     CGroup: /system.slice/systemd-resolved.service
             └─1079 /lib/systemd/systemd-resolved

May 22 15:10:08 j systemd[1]: Starting Network Name Resolution...
May 22 15:10:08 j systemd-resolved[1079]: Positive Trust Anchors:
May 22 15:10:08 j systemd-resolved[1079]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7>
May 22 15:10:08 j systemd-resolved[1079]: Negative trust anchors: home.arpa 10.in-addr.arpa 16.172.in-addr.arpa 17.172>
May 22 15:10:08 j systemd-resolved[1079]: Using system hostname 'j'.
May 22 15:10:08 j systemd[1]: Started Network Name Resolution.

Then, started the upgrade (using the tarball for the reasons mentioned in test plan):

root@j:~# wget http://archive.ubuntu.com/ubuntu/dists/noble-proposed/main/dist-upgrader-all/24.04.18/noble.tar.gz
--2024-05-22 15:10:36-- http://archive.ubuntu.com/ubuntu/dists/noble-proposed/main/dist-upgrader-all/24.04.18/noble.tar.gz
Resolving archive.ubuntu.com (archive.ubuntu.com)... 185.125.190.39, 91.189.91.82, 185.125.190.36, ...
Connecting to archive.ubuntu.com (archive.ubuntu.com)|185.125.190.39|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1274850 (1.2M) [application/x-gzip]
Saving to: ‘noble.tar.gz’

noble.tar.gz 100%[================================================>] 1.21M 1.73MB/s in 0.7s

2024-05-22 15:10:37 (1.73 MB/s) - ‘noble.tar.gz’ saved [1274850/1274850]

root@j:~# tar xf noble.tar.gz
root@j:~# ./noble --frontend DistUpgradeViewNonInteractive
[ ... ]

After the upgrade was complete:

root@j:~# systemctl status systemd-resolved
● systemd-resolved.service - Network Name Reso...

I have verified the fix using 255.4-1ubuntu8.1 from noble-proposed. I created a LXD jammy container:

root@j:~# cat /etc/os-release 
PRETTY_NAME="Ubuntu 22.04.4 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.4 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=jammy

And then disabled the stub-resolver according to the test plan:

root@j:~# mkdir -p /etc/systemd/resolved.conf.d/
root@j:~# cat > /etc/systemd/resolved.conf.d/no-stub-resolver.conf << EOF
[Resolve]
DNSStubListener=no
EOF
root@j:~# ln -sf /run/systemd/resolve/resolv.conf /etc/resolv.conf
root@j:~# systemctl restart systemd-resolved
root@j:~# systemctl status systemd-resolved
● systemd-resolved.service - Network Name Resolution
     Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled)
     Active: active (running) since Wed 2024-05-22 15:10:08 UTC; 19s ago
       Docs: man:systemd-resolved.service(8)
             man:org.freedesktop.resolve1(5)
             https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
             https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients
   Main PID: 1079 (systemd-resolve)
     Status: "Processing requests..."
      Tasks: 1 (limit: 18947)
     Memory: 4.5M
        CPU: 57ms
     CGroup: /system.slice/systemd-resolved.service
             └─1079 /lib/systemd/systemd-resolved

May 22 15:10:08 j systemd[1]: Starting Network Name Resolution...
May 22 15:10:08 j systemd-resolved[1079]: Positive Trust Anchors:
May 22 15:10:08 j systemd-resolved[1079]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7>
May 22 15:10:08 j systemd-resolved[1079]: Negative trust anchors: home.arpa 10.in-addr.arpa 16.172.in-addr.arpa 17.172>
May 22 15:10:08 j systemd-resolved[1079]: Using system hostname 'j'.
May 22 15:10:08 j systemd[1]: Started Network Name Resolution.

Then, started the upgrade (using the tarball for the reasons mentioned in test plan):

root@j:~# wget http://archive.ubuntu.com/ubuntu/dists/noble-proposed/main/dist-upgrader-all/24.04.18/noble.tar.gz
--2024-05-22 15:10:36--  http://archive.ubuntu.com/ubuntu/dists/noble-proposed/main/dist-upgrader-all/24.04.18/noble.tar.gz
Resolving archive.ubuntu.com (archive.ubuntu.com)... 185.125.190.39, 91.189.91.82, 185.125.190.36, ...
Connecting to archive.ubuntu.com (archive.ubuntu.com)|185.125.190.39|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1274850 (1.2M) [application/x-gzip]
Saving to: ‘noble.tar.gz’

noble.tar.gz                  100%[================================================>]   1.21M  1.73MB/s    in 0.7s

2024-05-22 15:10:37 (1.73 MB/s) - ‘noble.tar.gz’ saved [1274850/1274850]

root@j:~# tar xf noble.tar.gz
root@j:~# ./noble --frontend DistUpgradeViewNonInteractive
[ ... ]

After the upgrade was complete:

root@j:~# systemctl status systemd-resolved
● systemd-resolved.service - Network Name Resolution
     Loaded: loaded (/usr/lib/systemd/system/systemd-resolved.service; enabled; preset: enabled)
     Active: active (running) since Wed 2024-05-22 15:17:26 UTC; 15min ago
       Docs: man:systemd-resolved.service(8)
             man:org.freedesktop.resolve1(5)
             https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
             https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients
   Main PID: 1076 (systemd-resolve)
     Status: "Processing requests..."
      Tasks: 1 (limit: 18947)
     Memory: 4.6M (peak: 5.1M)
        CPU: 63ms
     CGroup: /system.slice/systemd-resolved.service
             └─1076 /lib/systemd/systemd-resolved

May 22 15:17:26 j systemd[1]: Starting Network Name Resolution...
May 22 15:17:26 j systemd-resolved[1076]: Positive Trust Anchors:
May 22 15:17:26 j systemd-resolved[1076]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7>
May 22 15:17:26 j systemd-resolved[1076]: Negative trust anchors: home.arpa 10.in-addr.arpa 16.172.in-addr.arpa 17.172>
May 22 15:17:26 j systemd-resolved[1076]: Using system hostname 'j'.
May 22 15:17:26 j systemd[1]: Started Network Name Resolution.
root@j:~# cat /etc/resolv.conf 
# This is /run/systemd/resolve/resolv.conf managed by man:systemd-resolved(8).
# Do not edit.
#
# This file might be symlinked as /etc/resolv.conf. If you're looking at
# /etc/resolv.conf and seeing this text, you have followed the symlink.
#
# This is a dynamic resolv.conf file for connecting local clients directly to
# all known uplink DNS servers. This file lists all configured search domains.
#
# Third party programs should typically not access this file directly, but only
# through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a
# different way, replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.

nameserver 10.19.111.1
nameserver fd42:3cda:638d:a9b3::1
nameserver fe80::216:3eff:fe07:85b6%29
search lxd
root@j:~# apt policy systemd-resolved
systemd-resolved:
  Installed: 255.4-1ubuntu8.1
  Candidate: 255.4-1ubuntu8.1
  Version table:
 *** 255.4-1ubuntu8.1 500
        500 http://archive.ubuntu.com/ubuntu noble-proposed/main amd64 Packages
        100 /var/lib/dpkg/status
     255.4-1ubuntu8 500
        500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages
root@j:~# grep "resolv.conf" /var/log/dist-upgrade/apt-term.log 
Converting /etc/resolv.conf to a symlink to /run/systemd/resolve/stub-resolv.conf...
cp: '/etc/resolv.conf' and '/run/systemd/resolve/stub-resolv.conf' are the same file
Cannot copy /etc/resolv.conf to /run/systemd/resolve/stub-resolv.conf

So, we see that (a) the user's choice to disable stub-resolver is still in place, and (b) the failed cp is non-fatal during the upgrade.

tags:

added: verification-done-noble
removed: verification-needed-noble

Revision history for this message

Ubuntu SRU Bot (ubuntu-sru-bot) wrote on 2024-05-23: Autopkgtest regression report (systemd/255.4-1ubuntu8.1)

#9

Download full text (4.9 KiB)

All autopkgtests for the newly accepted systemd (255.4-1ubuntu8.1) for noble have finished running.
The following regressions have been reported in tests triggered by the package:

389-ds-base/unknown (armhf, s390x)
aide/unknown (s390x)
amavisd-new/unknown (s390x)
apport/2.28.1-0ubuntu3 (arm64)
apport/unknown (s390x)
appstream/unknown (s390x)
apt/2.7.14build2 (armhf)
apt/unknown (s390x)
asterisk/unknown (s390x)
at-spi2-core/unknown (s390x)
ayatana-indicator-session/unknown (s390x)
bind9/unknown (amd64, armhf, i386, s390x)
bolt/unknown (amd64, s390x)
casper/unknown (s390x)
casync/unknown (s390x)
ceph/unknown (s390x)
clamav/unknown (amd64)
clevis/unknown (s390x)
cloudflare-ddns/unknown (s390x)
clutter-1.0/unknown (amd64)
cockpit/unknown (s390x)
collectd/unknown (s390x)
colord/unknown (s390x)
comitup/unknown (amd64, s390x)
conntrack-tools/unknown (amd64)
corosync/3.1.7-1ubuntu3 (arm64)
corosync/unknown (s390x)
corosync-qdevice/unknown (amd64, s390x)
coturn/unknown (armhf, s390x)
cron/unknown (ppc64el, s390x)
crun/unknown (amd64, s390x)
cryptsetup/2:2.7.0-1ubuntu4 (arm64)
csync2/unknown (amd64, s390x)
cups/unknown (amd64, s390x)
dbus/1.14.10-4ubuntu4 (i386)
dbus/unknown (amd64, armhf, s390x)
dbus-broker/unknown (amd64, s390x)
debos/unknown (amd64)
dhcpcd/unknown (armhf, s390x)
dlm/unknown (amd64)
dovecot/unknown (amd64)
dpdk/23.11-1build3 (amd64)
dq/20240101-1 (amd64)
exim4/unknown (amd64, armhf)
expeyes/unknown (amd64)
fcgiwrap/unknown (amd64)
fluidsynth/unknown (amd64, i386)
freedom-maker/unknown (amd64, armhf, i386)
freedombox/unknown (amd64)
freeradius/unknown (amd64)
fwupd/unknown (amd64)
gamemode/unknown (i386)
gdm3/unknown (amd64)
golang-github-coreos-go-systemd/unknown (amd64)
gpsd/unknown (amd64)
gvfs/unknown (s390x)
haproxy/unknown (amd64)
hddemux/unknown (amd64)
hwloc/unknown (amd64, s390x)
incus/unknown (amd64)
init-system-helpers/unknown (amd64)
initramfs-tools/unknown (amd64)
interception-tools/unknown (amd64)
janus/unknown (amd64)
keyman/unknown (amd64)
knot/unknown (amd64)
knot-resolver/unknown (amd64)
libcamera/0.2.0-3fakesync1build6 (amd64, armhf)
libei/1.2.1-1 (amd64)
libinput/unknown (amd64)
liblinux-systemd-perl/unknown (amd64)
libreswan/unknown (amd64)
libsdl2/unknown (amd64)
libsfml/2.6.1+dfsg-2build2 (armhf)
libsfml/unknown (amd64)
libsoup2.4/2.74.3-6ubuntu1 (ppc64el)
libsoup2.4/unknown (amd64)
libsoup3/unknown (amd64)
libusbauth-configparser/unknown (amd64)
libvirt/unknown (amd64)
lighttpd/unknown (amd64)
linux-ibm/unknown (amd64)
logiops/unknown (amd64)
logrotate/unknown (amd64)
mariadb/unknown (amd64)
mediawiki/unknown (amd64)
mir/unknown (amd64)
mkosi/unknown (amd64)
monitoring-plugins-systemd/unknown (amd64)
mosquitto/unknown (amd64)
multipath-tools/unknown (amd64)
munin/unknown (amd64)
mutter/unknown (amd64)
nagios-tang/unknown (amd64, s390x)
ndctl/unknown (armhf, s390x)
network-manager/unknown (amd64, s390x)
nextepc/unknown (amd64)
nix/unknown (amd64, armhf)
nut/unknown (amd64, armhf, s390x)
open-build-service/unknown (amd64)
openssh/unknown (amd64)
openvpn/unknown (amd64)
openzwave/unknown (amd64)
ovn/unknown (amd64)
pam/unknown (amd64, i386)
pdns-recursor/unknown (amd64)
pgagroal/unknown (amd64)
pgbouncer/unknown ...

All autopkgtests for the newly accepted systemd (255.4-1ubuntu8.1) for noble have finished running.
The following regressions have been reported in tests triggered by the package:

389-ds-base/unknown (armhf, s390x)
aide/unknown (s390x)
amavisd-new/unknown (s390x)
apport/2.28.1-0ubuntu3 (arm64)
apport/unknown (s390x)
appstream/unknown (s390x)
apt/2.7.14build2 (armhf)
apt/unknown (s390x)
asterisk/unknown (s390x)
at-spi2-core/unknown (s390x)
ayatana-indicator-session/unknown (s390x)
bind9/unknown (amd64, armhf, i386, s390x)
bolt/unknown (amd64, s390x)
casper/unknown (s390x)
casync/unknown (s390x)
ceph/unknown (s390x)
clamav/unknown (amd64)
clevis/unknown (s390x)
cloudflare-ddns/unknown (s390x)
clutter-1.0/unknown (amd64)
cockpit/unknown (s390x)
collectd/unknown (s390x)
colord/unknown (s390x)
comitup/unknown (amd64, s390x)
conntrack-tools/unknown (amd64)
corosync/3.1.7-1ubuntu3 (arm64)
corosync/unknown (s390x)
corosync-qdevice/unknown (amd64, s390x)
coturn/unknown (armhf, s390x)
cron/unknown (ppc64el, s390x)
crun/unknown (amd64, s390x)
cryptsetup/2:2.7.0-1ubuntu4 (arm64)
csync2/unknown (amd64, s390x)
cups/unknown (amd64, s390x)
dbus/1.14.10-4ubuntu4 (i386)
dbus/unknown (amd64, armhf, s390x)
dbus-broker/unknown (amd64, s390x)
debos/unknown (amd64)
dhcpcd/unknown (armhf, s390x)
dlm/unknown (amd64)
dovecot/unknown (amd64)
dpdk/23.11-1build3 (amd64)
dq/20240101-1 (amd64)
exim4/unknown (amd64, armhf)
expeyes/unknown (amd64)
fcgiwrap/unknown (amd64)
fluidsynth/unknown (amd64, i386)
freedom-maker/unknown (amd64, armhf, i386)
freedombox/unknown (amd64)
freeradius/unknown (amd64)
fwupd/unknown (amd64)
gamemode/unknown (i386)
gdm3/unknown (amd64)
golang-github-coreos-go-systemd/unknown (amd64)
gpsd/unknown (amd64)
gvfs/unknown (s390x)
haproxy/unknown (amd64)
hddemux/unknown (amd64)
hwloc/unknown (amd64, s390x)
incus/unknown (amd64)
init-system-helpers/unknown (amd64)
initramfs-tools/unknown (amd64)
interception-tools/unknown (amd64)
janus/unknown (amd64)
keyman/unknown (amd64)
knot/unknown (amd64)
knot-resolver/unknown (amd64)
libcamera/0.2.0-3fakesync1build6 (amd64, armhf)
libei/1.2.1-1 (amd64)
libinput/unknown (amd64)
liblinux-systemd-perl/unknown (amd64)
libreswan/unknown (amd64)
libsdl2/unknown (amd64)
libsfml/2.6.1+dfsg-2build2 (armhf)
libsfml/unknown (amd64)
libsoup2.4/2.74.3-6ubuntu1 (ppc64el)
libsoup2.4/unknown (amd64)
libsoup3/unknown (amd64)
libusbauth-configparser/unknown (amd64)
libvirt/unknown (amd64)
lighttpd/unknown (amd64)
linux-ibm/unknown (amd64)
logiops/unknown (amd64)
logrotate/unknown (amd64)
mariadb/unknown (amd64)
mediawiki/unknown (amd64)
mir/unknown (amd64)
mkosi/unknown (amd64)
monitoring-plugins-systemd/unknown (amd64)
mosquitto/unknown (amd64)
multipath-tools/unknown (amd64)
munin/unknown (amd64)
mutter/unknown (amd64)
nagios-tang/unknown (amd64, s390x)
ndctl/unknown (armhf, s390x)
network-manager/unknown (amd64, s390x)
nextepc/unknown (amd64)
nix/unknown (amd64, armhf)
nut/unknown (amd64, armhf, s390x)
open-build-service/unknown (amd64)
openssh/unknown (amd64)
openvpn/unknown (amd64)
openzwave/unknown (amd64)
ovn/unknown (amd64)
pam/unknown (amd64, i386)
pdns-recursor/unknown (amd64)
pgagroal/unknown (amd64)
pgbouncer/unknown (amd64)
pglistener/unknown (amd64)
php8.3/unknown (amd64)
pipewire/unknown (amd64)
policykit-1/unknown (amd64)
polkit-qt-1/unknown (amd64)
postgresql-16/unknown (amd64, s390x)
procps/unknown (armhf)
prometheus-homeplug-exporter/unknown (armhf)
prometheus-postfix-exporter/0.3.0-4build1 (armhf)
pulseaudio/unknown (amd64)
puppet-agent/unknown (armhf)
pystemd/0.13.2-1build2 (armhf)
pystemd/unknown (amd64, s390x)
python-dbusmock/unknown (s390x)
python-sdbus/unknown (s390x)
python-systemd/unknown (s390x)
pyudev/unknown (amd64, s390x)
qlcplus/unknown (amd64, armhf, s390x)
rbldnsd/unknown (amd64, armhf, s390x)
redis/unknown (amd64)
remctl/unknown (amd64, s390x)
rsyslog/8.2312.0-3ubuntu9 (amd64)
rtkit/unknown (s390x)
rust-whoami/unknown (amd64)
samba/2:4.19.5+dfsg-4ubuntu9 (arm64)
samba/unknown (s390x)
seatd/unknown (i386)
shibboleth-sp/unknown (s390x)
sks/unknown (s390x)
smcroute/unknown (amd64, s390x)
snapd/unknown (s390x)
squid/unknown (s390x)
sssd/unknown (amd64)
stayrtr/unknown (s390x)
strongswan/unknown (amd64, arm64)
stunnel4/unknown (amd64)
tgt/unknown (amd64, s390x)
tinyssh/20240101-2 (arm64, s390x)
tinyssh/unknown (amd64)
tmux/unknown (s390x)
tpm2-abrmd/unknown (amd64, s390x)
udisks2/unknown (amd64)
umockdev/unknown (amd64, s390x)
upower/1.90.3-1 (armhf)
upower/unknown (s390x)
usbauth/unknown (amd64, s390x)
util-linux/unknown (amd64)
vlc/3.0.20-3build6 (arm64)
vlc/unknown (i386)
weston/unknown (amd64)
yder/unknown (s390x)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/noble/update_excuses.html#systemd

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

Ubuntu
systemd package

package systemd-resolved 253.5-1ubuntu7 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 [cp: '/etc/resolv.conf' and '/run/systemd/resolve/stub-resolv.conf' are the same file]

Bug Description

Duplicates of this bug

Other bug subscribers

Bug attachments

Remote bug watches

Affects		Status	Importance	Assigned to	Milestone
	systemd (Ubuntu)	Fix Committed	Undecided	Unassigned
	Noble	Fix Committed	High	Nick Rosbrook

Ubuntusystemd package

package systemd-resolved 253.5-1ubuntu7 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 [cp: '/etc/resolv.conf' and '/run/systemd/resolve/stub-resolv.conf' are the same file]

Bug Description

Duplicates of this bug

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
systemd package