systemd/ 245.4-4ubuntu3.22 ADT test failure with linux/5.4.0-156.173

[Roxana Nicolescu]

[Impact]

The armhf autopkgtest fails for focal and ultimately leads to less test coverage because other packages now won't block on these failures, and may not notice new regressions.

[Test Plan]

The test-execute test within root-unittests should pass.

[Where problems could occur]

The patch only changes a service file in the test tree of systemd, so this is not a change that will be seen on real Ubuntu systems. Hence any further problems would be seen only in the test-execute test.

[Original Description]

This is a scripted bug report about ADT failures while running systemd tests for linux/5.4.0-156.173 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined.
root-unittests fails.

Testing failed on:
    armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20230727_150132_9cd77@/log.gz

[Nick Rosbrook (enr0n)]

I believe this is the relevant part from test-execute:

1739s exec-dynamicuser-statedir.service: About to execute: /usr/bin/sh -x -c 'test $$(find / \( -path /var/tmp -o -path /tmp -o -path /proc -o -path /dev/mqueue -o -path /dev/shm -o -path /sys/fs/bpf -o -path /dev/.lxc \) -prune -o -type d -writable -print 2>/dev/null | sort -u | tr -d \\n) = /var/lib/private/quux/pief/var/lib/private/waldo'
1739s exec-dynamicuser-statedir.service: Forked /usr/bin/sh as 1374
1739s PR_SET_MM_ARG_START failed, attempting PR_SET_MM_ARG_END hack: Operation not permitted
1739s PR_SET_MM_ARG_END hack failed, proceeding without: Operation not permitted
1739s exec-dynamicuser-statedir.service: User lookup succeeded: uid=65325 gid=65325
1742s Received SIGCHLD from PID 1374 (sh).
1742s Child 1374 (sh) died (code=exited, status=1/FAILURE)
1742s exec-dynamicuser-statedir.service: Failed to read oom_kill field of memory.events cgroup attribute: No such file or directory
1742s exec-dynamicuser-statedir.service: Child 1374 belongs to exec-dynamicuser-statedir.service.
1742s exec-dynamicuser-statedir.service: Main process exited, code=exited, status=1/FAILURE
1742s exec-dynamicuser-statedir.service: Failed with result 'exit-code'.
1742s exec-dynamicuser-statedir.service: Service will not restart (restart setting)
1742s exec-dynamicuser-statedir.service: Changed start -> failed
1742s exec-dynamicuser-statedir.service: Unit entered failed state.
1742s Spawning thread to nuke /tmp/systemd-private-e386f1fc8bcf4249b2d714258658fd11-exec-dynamicuser-statedir.service-h9gSex
1742s Spawning thread to nuke /var/tmp/systemd-private-e386f1fc8bcf4249b2d714258658fd11-exec-dynamicuser-statedir.service-Hof62v
1742s UID 65325 is no longer referenced, cleaning up its IPC.
1742s GID 65325 is no longer referenced, cleaning up its IPC.
1742s Failed to connect to nscd socket: No such file or directory
1742s Failed to connect to nscd socket: No such file or directory
1742s test_exec_dynamicuser: exec-dynamicuser-statedir.service: exit status 1, expected 0
1743s FAIL: test-execute (code: 134)
1743s Aborted (core dumped)

Not sure what the cause is yet.

[Nick Rosbrook (enr0n)]

This is fixed by upstream commit [1], which is included in v251 and newer. The reason this is not needed in Jammy (v249) is because we already have a patch [2] that causes this test case to be skipped on arhmf.

[1] https://github.com/systemd/systemd/commit/646cba5c4208c28c56dbe52d676ab1a176c69b7f
[2] https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/tree/debian/patches/debian/UBUNTU-src-test-test-execute.c-Skip-parts-of-test-execute-in-con.patch?h=ubuntu-jammy

[Brian Murray (brian-murray)]

Hello Roxana, or anyone else affected,

Accepted systemd into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.23 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-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. 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.

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.23) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

casync/2+20190213-1 (armhf)
gvfs/1.44.1-1ubuntu1.2 (ppc64el)
linux-gcp-5.15/5.15.0-1048.56~20.04.1 (arm64)
linux-hwe-5.15/5.15.0-91.101~20.04.1 (armhf)
linux-oracle-5.15/5.15.0-1049.55~20.04.1 (arm64)
mariadb-10.3/1:10.3.38-0ubuntu0.20.04.1 (armhf)
netplan.io/0.104-0ubuntu2~20.04.4 (s390x)
puppet/5.5.10-4ubuntu3 (armhf)
upower/0.99.11-1build2 (armhf)

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/focal/update_excuses.html#systemd

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

Thank you!

[Nick Rosbrook (enr0n)]

The autopkgtest for systemd 245.4-4ubuntu3.23 on armhf passed, which verifies this fix: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20240110_171824_cbc46@/log.gz.

[Launchpad Janitor (janitor)]

This bug was fixed in the package systemd - 245.4-4ubuntu3.23

---------------
systemd (245.4-4ubuntu3.23) focal; urgency=medium

  [ Nick Rosbrook ]
  * core/device: ignore DEVICE_FOUND_UDEV bit on switching root (LP: #2037281)
    File: debian/patches/lp2037281-core-device-ignore-DEVICE_FOUND_UDEV-bit-on-switching-roo.patch
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=7793563bb38a84a3dc6bc0da1c08546c3b915ab8
  * dns-query: bump CNAME_MAX to 16 (LP: #2024009)
    File: debian/patches/lp2024009-dns-query-bump-CNAME_MAX-to-16.patch
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=193899d103d44c642d362e9916b14df844ec702f
  * Fall back to kexec when no kexec binary exists (LP: #1969365)
    File: debian/patches/lp1969365-Fall-back-to-kexec-when-no-kexec-binary-exists.patch
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=3934f3794427dee4e72824998dd4c6e6d5875289
  * test: ignore LXC filesystem when checking for writable locations (LP: #2029352)
    File: debian/patches/lp2029352-test-ignore-LXC-filesystem-when-checking-for-writable-loc.patch
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=70facbfbf54c4ffb31ba392dbe3fec3084fdf3bc

  [ Heitor Alves de Siqueira ]
  * core/mount: adjust deserialized state based on /proc/self/mountinfo (LP: #1837227)
    Author: Heitor Alves de Siqueira
    File: debian/patches/lp1837227-core-mount-adjust-deserialized-state-based-on-proc-self-m.patch
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=a0a749953d309f48bc45140102adf205d1071c4d

 -- Nick Rosbrook <email address hidden> Tue, 21 Nov 2023 16:10:21 -0500

[Łukasz Zemczak (sil2100)]

The verification of the Stable Release Update for systemd has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.