systemd: networkd-test.py fails with newer kinetic kernels
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
Kinetic |
Won't Fix
|
Undecided
|
Unassigned | ||
systemd (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Kinetic |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
systemd autopkgtests are failing in kinetic, and they are not considered regressions. The failing test is one within networkd-test.py:
=======
ERROR: test_resolved_
resolved: domain-restricted DNS servers
-------
Traceback (most recent call last):
File "/tmp/autopkgte
out = subprocess.
File "/usr/lib/
return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
File "/usr/lib/
raise CalledProcessEr
subprocess.
-------
Ran 35 tests in 161.770s
FAILED (errors=1, skipped=2)
The failures started without any changes to the systemd package, i.e. it was caused by another package upload. In particular, the failures started around 2022-11-17 with linux 5.19.0-24.25. The tests pass fine with linux 5.19.0-21.21, i.e. the version in kinetic-release.
This can be demonstrated locally with autopkgtest:
$ autopkgtest --shell-fail systemd --test-name networkd-test.py --pin-packages=
Note in the above command I did not pass -U, so no packages in the test bed are upgraded. But, with:
$ autopkgtest --shell-fail systemd --test-name networkd-test.py -U -- qemu /home/nr/
the kernel is upgraded, and the test fails.
This can also be done manually by grabbing the systemd source on a kinetic machine (e.g. pull-lp-source systemd kinetic), and running:
$ sudo python3 test/networkd-
The attached journal.txt shows systemd-resolved logs from when the test is run. The failure is caused by the EHOSTUNREACH when trying to resolve math.lab.
---
ProblemType: Bug
AlsaDevices:
total 0
crw-rw---- 1 root audio 116, 1 Mar 9 11:56 seq
crw-rw---- 1 root audio 116, 33 Mar 9 11:56 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5CheckR
DistroRelease: Ubuntu 22.10
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb: Error: command ['lsusb'] failed with exit code 1:
Lsusb-t:
Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=xterm-
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 bochs-drmdrmfb
ProcKernelCmdLine: BOOT_IMAGE=
ProcVersionSign
RelatedPackageV
linux-
linux-
linux-firmware 20220923.
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
Tags: kinetic
Uname: Linux 5.19.0-35-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 04/01/2014
dmi.bios.release: 0.0
dmi.bios.vendor: SeaBIOS
dmi.bios.version: 1.16.0-
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.
dmi.modalias: dmi:bvnSeaBIOS:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.
dmi.sys.vendor: QEMU
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 2009859
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.