test-execute fails because of apparmor unprivileged userns restrictions
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| systemd (Ubuntu) |
Fix Committed
|
Undecided
|
Nick Rosbrook | ||
| Noble |
Fix Released
|
Medium
|
Nick Rosbrook | ||
Bug Description
[Impact]
unit-tests in noble currently fails because test-execute fails with the following:
1633s exec-basic.service: Child 1934 belongs to exec-basic.service.
1633s exec-basic.service: Control process exited, code=exited, status=0/SUCCESS (success)
1633s exec-basic.service: Got final SIGCHLD for state start-post.
1633s exec-basic.service: Deactivated successfully.
1633s exec-basic.service: Service will not restart (restart setting)
1633s exec-basic.service: Changed start-post -> dead
1633s exec-basic.service: Consumed 49ms CPU time.
1633s Spawning process to nuke '/tmp/systemd-
1633s Successfully forked off intermediary '(sd-rmrf)' as PID 1936.
1633s Spawning process to nuke '/var/tmp/
1633s Successfully forked off intermediary '(sd-rmrf)' as PID 1937.
1633s src/test/
1633s Skipping PR_SET_MM, as we don't have privileges.
1633s Skipping PR_SET_MM, as we don't have privileges.
1633s (test-execute-
1633s Assertion 'r >= 0' failed at src/test/
1633s
[...]
1678s [1mOK: 288 SKIP: 6 FAIL: 1[0m
1679s autopkgtest [20:59:40]: test unit-tests: -------
1679s autopkgtest [20:59:40]: test unit-tests: - - - - - - - - - - results - - - - - - - - - -
1679s unit-tests FAIL non-zero exit status 1
This is because some tests in test-execute run unprivileged, and try to user user namespaces. I fixed this upstream[1], so just backport the patch so that this test case no longer fails.
[Test Plan]
This only pertains to the unit-tests autopkgtest in systemd. Just check the result of the autopkgtest run.
[Where problems could occur]
This only changes the test-execute code to skip tests that require unprivileged userns whenever kernel.
[Other information]
Note that the upstream-2 test still has regular failures which need to be investigated, so this change will not get the systemd autopkgtests back to green. Since I already fixed this upstream, it is easy to backport, so it's worth making the incremental improvement for now.
[1] https:/
| Changed in systemd (Ubuntu): | |
| status: | New → Fix Committed |
| Changed in systemd (Ubuntu Noble): | |
| status: | New → Triaged |
| assignee: | nobody → Nick Rosbrook (enr0n) |
| importance: | Undecided → Medium |
| Changed in systemd (Ubuntu Noble): | |
| status: | Triaged → In Progress |
| Łukasz Zemczak (sil2100) wrote Please test proposed package | #1 |
| Changed in systemd (Ubuntu Noble): | |
| status: | In Progress → Fix Committed |
| tags: | added: verification-needed verification-needed-noble |
| Ubuntu SRU Bot (ubuntu-sru-bot) wrote Autopkgtest regression report (systemd/255.4-1ubuntu8.1) | #2 |
| Nick Rosbrook (enr0n) wrote | #3 |
| tags: |
added: verification-done verification-done-noble removed: verification-needed verification-needed-noble |
| Nick Rosbrook (enr0n) wrote | #4 |
| Launchpad Janitor (janitor) wrote | #5 |
| Changed in systemd (Ubuntu Noble): | |
| status: | Fix Committed → Fix Released |
| Brian Murray (brian-murray) wrote Update Released | #6 |
Hello Nick, or anyone else affected,
Accepted systemd into noble-proposed. The package will build now and be available at https:/
Please help us by testing this new package. See https:/
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-
Further information regarding the verification process can be found at https:/
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.