Repository navigation
test/system: Unbreak DNS in Arch Linux containers on Ubuntu 22.04 hosts - #1859
Merged
debarshiray merged 1 commit intoNov 17, 2026
Conversation
debarshiray
marked this pull request as draft
November 13, 2026 14:55
Currently, the DNS test in Arch Linux containers fails on Ubuntu 22.04
hosts:
not ok 184 network: DNS inside Arch Linux in 715ms
# tags: arch-fedora runtime-environment
# (from function `assert_line' in file
test/system/libs/bats-assert/src/assert.bash, line 488,
# in test file test/system/203-network.bats, line 283)
# `assert_line --index 0 "$ipv4_addr"' failed
#
# -- line differs --
# index : 0
# expected : 193.0.14.129
# actual :
# --
#
This is because the underlying resolvectl(1) invocation fails:
$ resolvectl --legend false --no-pager --type A query
k.root-servers.net
k.root-servers.net: resolve call failed:
org.varlink.service.MethodNotFound
In systemd 262, resolvectl(1) was changed to communicate with
systemd-resolved(8) using Varlink APIs instead of their D-Bus
counterparts. One of them was the ResolveRecord method [1], known as
io.systemd.Resolve.ResolveRecord in the Varlink API and as
org.freedesktop.resolve1.Manager.ResolveRecord in the D-Bus variant.
However, the ResolveRecord method was only exposed through Varlink in
systemd 256 [2] and Ubuntu 22.04 only has systemd 249. This breaks the
compatibility between resolvectl(1) and systemd-resolved(8).
It seems that these days the arch-toolbox image includes python3(1),
which it originally didn't, and the nss-resolve(8) plugin for the GNU
Name Service Switch (or NSS) functionality of the GNU C Library doesn't
use ResolveRecord. Therefore, resolvectl(1) can be replaced by using
getaddrinfo(3), which is a front-end to nss-resolve(8), through
python3(1).
[1] systemd commit cfac7ec169892b38
systemd/systemd@cfac7ec169892b38
systemd/systemd#41840
[2] systemd commit cf1c8cdb87d4e2c1
systemd/systemd@cf1c8cdb87d4e2c1
systemd/systemd#31616
containers#1859
debarshiray
force-pushed
the
wip/rishi/test-system-203-network-unbreak-archlinux-ubuntu-2204-dns
branch
from
November 17, 2026 00:01
551876f to
1c49907
Compare
debarshiray
marked this pull request as ready for review
November 17, 2026 00:07
Rolv-Apneseth
approved these changes
Nov 17, 2026
Member
Author
|
Thanks for the review, @Rolv-Apneseth ! |
debarshiray
deleted the
wip/rishi/test-system-203-network-unbreak-archlinux-ubuntu-2204-dns
branch
November 17, 2026 12:21
Contributor
|
Np thanks for the fix. Will you be modifying #1847 / opening a new PR, or do you want me to remove the |
Member
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Currently, the DNS test in Arch Linux containers fails on Ubuntu 22.04
hosts:
This is because the underlying
resolvectl(1)invocation fails:In systemd 262,
resolvectl(1)was changed to communicate withsystemd-resolved(8)using Varlink APIs instead of their D-Buscounterparts. One of them was the
ResolveRecordmethod [1], known asio.systemd.Resolve.ResolveRecordin the Varlink API and asorg.freedesktop.resolve1.Manager.ResolveRecordin the D-Bus variant.However, the
ResolveRecordmethod was only exposed through Varlink insystemd 256 [2] and Ubuntu 22.04 only has systemd 249. This breaks the
compatibility between
resolvectl(1)andsystemd-resolved(8).It seems that these days the
arch-toolboximage includespython3(1),which it originally didn't, and the
nss-resolve(8)plugin for the GNUName Service Switch (or NSS) functionality of the GNU C Library doesn't
use
ResolveRecord. Therefore,resolvectl(1)can be replaced by usinggetaddrinfo(3), which is a front-end tonss-resolve(8), throughpython3(1).[1] systemd commit cfac7ec169892b38
systemd/systemd@cfac7ec169892b38
systemd/systemd#41840
[2] systemd commit cf1c8cdb87d4e2c1
systemd/systemd@cf1c8cdb87d4e2c1
systemd/systemd#31616