systemd test_exec_umask_namespace fails in privileged container

Bug #1959013 reported by Lukas Märdian
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
lxd (Ubuntu)
New
Undecided
Unassigned
systemd (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

systemd added a new test case to it's "test-execute", which is failing in privileged containers, while passing everywhere else.

https://github.com/systemd/systemd-stable/commit/ae53f4b5e48860b473c4d05958486a77f84ecc6d

exec-umask-namespace.service: Passing 0 fds to service
exec-umask-namespace.service: About to execute /bin/ls -lahd /tmp/subdir
exec-umask-namespace.service: Forked /bin/ls as 2485
exec-umask-namespace.service: Changed dead -> start
exec-umask-namespace.service: User lookup succeeded: uid=65534 gid=65534
Received SIGCHLD from PID 2485 (ls).
Child 2485 (ls) died (code=exited, status=2/INVALIDARGUMENT)
exec-umask-namespace.service: Failed to read oom_kill field of memory.events cgroup attribute: No such file or directory
exec-umask-namespace.service: Child 2485 belongs to exec-umask-namespace.service.
exec-umask-namespace.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
exec-umask-namespace.service: Failed with result 'exit-code'.
exec-umask-namespace.service: Service will not restart (restart setting)
exec-umask-namespace.service: Changed start -> failed
exec-umask-namespace.service: Unit entered failed state.
src/test/test-execute.c:868:test_exec_umask_namespace: exec-umask-namespace.service: exit status 2, expected 0

A full test-run / log is available at https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-slyon-testing/jammy/amd64/s/systemd/20220125_143301_25947@/log.gz

I'll be skipping this test case fow now, to be able to move forward with systemd 249.9

Revision history for this message
Christian Brauner (cbrauner) wrote :

Are the tests run with security.nesting=true set?

Revision history for this message
Lukas Märdian (slyon) wrote :

No I don't think so. It is only setting: lxc profile set default security.privileged "true"

See L60+: https://git.launchpad.net/ubuntu/+source/systemd/tree/debian/tests/tests-in-lxd#n60

would security.nesting be required in this case?

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package systemd - 249.9-0ubuntu2

---------------
systemd (249.9-0ubuntu2) jammy; urgency=medium

  * Skip flaky 55-OOMD test on ppc64el
    File: debian/patches/deny-list-TEST-55-OOMD-on-ppc64el.patch
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=211f8962ce89d416c2866444e0e2da794ecd5dd1

 -- Lukas Märdian <email address hidden> Fri, 28 Jan 2022 10:46:41 +0100

Changed in systemd (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.