Bug#1065624: resolved not working after installation, race with dbus and user creation

[Timo Weingärtner]

Package: systemd-resolved
Version: 252.22-1~deb12u1
Severity: important
X-Debbugs-Cc: timo.weingaertner at quantumsimulations.de

After installing systemd-resolved name resolution does not work anymore:
----8<----8<----
# apt-get --no-install-recommends install systemd-resolved
[…]
# host debian.org
Host debian.org not found: 2(SERVFAIL)
# resolvectl
Failed to get global data: Connection timed out
# systemctl restart systemd-resolved.service 
# host debian.org
debian.org has address […]
[…]
----8<----8<----

The relevant error message from dbus-daemon appears before postinst creates
the user and starts the service.

Maybe creating the user in preinst already, before it is referenced in
dbus config, would be better.

This is the log, including my workaround:
----8<----8<----
Mar 07 14:10:50 HOST python3(mitogen:[…])[45763]: ansible-apt Invoked with pkg=['systemd-resolved'] install_recommends=False package=['systemd-resolved'] state=present […]
Mar 07 14:10:51 HOST dbus-daemon[15599]: [system] Reloaded configuration
Mar 07 14:10:51 HOST dbus-daemon[15599]: [system] Reloaded configuration
Mar 07 14:10:51 HOST dbus-daemon[15599]: [system] Reloaded configuration
Mar 07 14:10:51 HOST dbus-daemon[15599]: Unknown username "systemd-resolve" in message bus configuration file
Mar 07 14:10:51 HOST dbus-daemon[15599]: [system] Reloaded configuration
Mar 07 14:10:51 HOST systemd[1]: Reloading.
Mar 07 14:10:52 HOST systemd[1]: Starting systemd-resolved.service - Network Name Resolution...
Mar 07 14:10:52 HOST systemd-resolved[46459]: Positive Trust Anchors:
Mar 07 14:10:52 HOST systemd-resolved[46459]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
Mar 07 14:10:52 HOST systemd-resolved[46459]: Negative trust anchors: home.arpa 10.in-addr.arpa […]
Mar 07 14:10:52 HOST systemd-resolved[46459]: Using system hostname 'HOST'.
Mar 07 14:10:52 HOST systemd[1]: Started systemd-resolved.service - Network Name Resolution.
Mar 07 14:10:52 HOST systemd[1]: Reached target nss-lookup.target - Host and Network Name Lookups.
Mar 07 14:10:52 HOST dbus-daemon[15599]: [system] Reloaded configuration
Mar 07 14:10:53 HOST python3(mitogen:[…])[45763]: ansible-systemd_service Invoked with unit=dbus.service state=reloaded name=dbus.service daemon_reload=False daemon_reexec=False scope=system no_block=False enabled=None force=None masked=None
Mar 07 14:10:53 HOST systemd[1]: Reloading dbus.service - D-Bus System Message Bus...
Mar 07 14:10:53 HOST dbus-daemon[15599]: [system] Reloaded configuration
Mar 07 14:10:53 HOST dbus-send[46517]: method return time=1709817053.651177 sender=org.freedesktop.DBus -> destination=:1.143 serial=3 reply_serial=2
Mar 07 14:10:53 HOST systemd[1]: Reloaded dbus.service - D-Bus System Message Bus.
Mar 07 14:10:53 HOST python3(mitogen:[…])[45763]: ansible-systemd_service Invoked with unit=systemd-resolved.service state=restarted name=systemd-resolved.service daemon_reload=False daemon_reexec=False scope=system no_block=False enabled=None force=None masked=None
Mar 07 14:10:53 HOST systemd[1]: Stopping systemd-resolved.service - Network Name Resolution...
Mar 07 14:10:53 HOST systemd[1]: systemd-resolved.service: Deactivated successfully.
Mar 07 14:10:53 HOST systemd[1]: Stopped systemd-resolved.service - Network Name Resolution.
Mar 07 14:10:53 HOST systemd[1]: Starting systemd-resolved.service - Network Name Resolution...
Mar 07 14:10:53 HOST systemd-resolved[46522]: Positive Trust Anchors:
Mar 07 14:10:53 HOST systemd-resolved[46522]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
Mar 07 14:10:53 HOST systemd-resolved[46522]: Negative trust anchors: home.arpa 10.in-addr.arpa […]
Mar 07 14:10:53 HOST systemd-resolved[46522]: Using system hostname 'HOST'.
Mar 07 14:10:53 HOST systemd[1]: Started systemd-resolved.service - Network Name Resolution.
Mar 07 14:10:53 HOST systemd-resolved[46522]: wlp[…]: Bus client set default route setting: yes
Mar 07 14:10:53 HOST systemd-resolved[46522]: wlp[…]: Bus client set DNS server list to: […]
Mar 07 14:10:53 HOST systemd-resolved[46522]: enx[…]: Bus client set search domain list to: […]
Mar 07 14:10:53 HOST systemd-resolved[46522]: enx[…]: Bus client set default route setting: yes
Mar 07 14:10:53 HOST systemd-resolved[46522]: enx[…]: Bus client set DNS server list to: […]
----8<----8<----


-- System Information:
Debian Release: 12.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-18-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en_US
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages systemd-resolved depends on:
ii  dbus [default-dbus-system-bus]  1.14.10-1~deb12u1
ii  libc6                           2.36-9+deb12u4
ii  libssl3                         3.0.11-1~deb12u2
ii  libsystemd-shared               252.22-1~deb12u1
ii  systemd                         252.22-1~deb12u1

Versions of packages systemd-resolved recommends:
pn  libnss-myhostname  <none>
pn  libnss-resolve     <none>

Versions of packages systemd-resolved suggests:
ii  policykit-1  122-3
ii  polkitd      122-3

-- no debconf information