systemd-run does not make the new scope unit part of the slice specified via the --slice arg
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
systemd |
Unknown
|
Unknown
|
|||
systemd (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Xenial |
Fix Released
|
Medium
|
Dan Streetman |
Bug Description
[impact]
running 'systemd-run --scope --slice=$SLICE $PROGRAM' does not start the program under $SLICE, instead it starts it under system.slice
[test case]
root:~# systemd-run --scope --slice=
Running scope as unit run-r16d872f1b0
^Z
[3]+ Stopped systemd-run --scope --slice=
root:~# bg
[3]+ systemd-run --scope --slice=
root:~# systemctl show -p Slice run-r16d872f1b0
Slice=system.slice
[regression potential]
This defers running the manager unit load queue when setting the slice for a transient unit, as well as actually passing the slice parameter over the bus when using --scope, so any regression would very likely involve incorrectly setting the slice for a scope and/or problems when processing transient units that specify a slice.
[scope]
this is needed only for Xenial.
this is fixed upstream by
https:/
which is included starting in v230, so is included in Bionic and later.
Changed in systemd (Ubuntu Xenial): | |
status: | New → In Progress |
Changed in systemd (Ubuntu): | |
status: | New → Fix Released |
Changed in systemd (Ubuntu Xenial): | |
assignee: | nobody → Dan Streetman (ddstreet) |
importance: | Undecided → Medium |
description: | updated |
Hello Dan, or anyone else affected,
Accepted systemd into xenial-proposed. The package will build now and be available at https:/ /launchpad. net/ubuntu/ +source/ systemd/ 229-4ubuntu21. 29 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- xenial to verification- done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed- xenial. 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/ PerformingSRUVe rification . 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.