[Touch-packages] [Bug 1881312] Re: systemd-run does not make the new scope unit part of the slice specified via the --slice arg
This bug was fixed in the package systemd - 229-4ubuntu21.29 --- systemd (229-4ubuntu21.29) xenial; urgency=medium [ Dan Streetman ] * d/p/lp1881312/0001-core-don-t-dispatch-load-queue-when-setting-Slice-fo.patch, d/p/lp1881312/0002-run-make-slice-work-in-conjunction-with-scope.patch: - run new scope unit in specified slice (LP: #1881312) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=b5a778c3cd93e3d684602146f281f315f30778a8 * d/p/lp1877176-sd-dhcp-client-validate-hostnames-stricter-7308.patch: - strictly validate hostname sent to dhcp server (LP: #1877176) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=7a1f1c41dcd860fcba6be42a2153cfe4315ebf17 * d/e/rules-ubuntu/40-vm-hotadd.rules: - Hotadd only offline memory and CPUs (LP: #1876018) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=43357bd260a1c3e7b4951d33cbacaebda1d086b3 * d/p/lp1698388-journal-remote-Ensure-reallocation-of-source-buf-doe.patch: - Fix assertion failure when journald source->filled < source->size (LP: #1698388) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=d1cc15b88113510227e5a76654e103ef54a8b8f3 [ Heitor Alves de Siqueira ] * d/p/lp1876600-sd-bus-deal-with-cookie-overruns.patch: - deal with dbus cookie overruns (LP: #1876600) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=8dc9ef188944349169044d8974a4ffa55c66be9d -- Heitor Alves de Siqueira Tue, 07 Jul 2020 17:28:11 -0400 ** Changed in: systemd (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1881312 Title: systemd-run does not make the new scope unit part of the slice specified via the --slice arg Status in systemd: Unknown Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released 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=user-1000.slice sleep 1000 Running scope as unit run-r16d872f1b0894b88a79421a890269e6c.scope. ^Z [3]+ Stopped systemd-run --scope --slice=user-1000.slice sleep 1000 root:~# bg [3]+ systemd-run --scope --slice=user-1000.slice sleep 1000 & root:~# systemctl show -p Slice run-r16d872f1b0894b88a79421a890269e6c.scope 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://github.com/systemd/systemd/pull/3094 which is included starting in v230, so is included in Bionic and later. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1881312/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1881312] Re: systemd-run does not make the new scope unit part of the slice specified via the --slice arg
xenial: root@lp1881312-x:~# dpkg -l systemd|grep systemd ii systemd229-4ubuntu21.28 amd64system and service manager root@lp1881312-x:~# systemd-run --scope --slice=user-1000.slice sleep 1000 Running scope as unit run-rad93ed3206334259a90708def087987d.scope. ^Z [1]+ Stopped systemd-run --scope --slice=user-1000.slice sleep 1000 root@lp1881312-x:~# bg [1]+ systemd-run --scope --slice=user-1000.slice sleep 1000 & root@lp1881312-x:~# systemctl show -p Slice run-rad93ed3206334259a90708def087987d.scope Slice=system.slice root@lp1881312-x:~# dpkg -l systemd|grep systemd ii systemd229-4ubuntu21.29 amd64system and service manager root@lp1881312-x:~# systemd-run --scope --slice=user-1000.slice sleep 1000 Running scope as unit run-r4648aaa0fdca485b9b1a2b9a5298fb0f.scope. ^Z [2]+ Stopped systemd-run --scope --slice=user-1000.slice sleep 1000 root@lp1881312-x:~# bg [2]+ systemd-run --scope --slice=user-1000.slice sleep 1000 & root@lp1881312-x:~# systemctl show -p Slice run-r4648aaa0fdca485b9b1a2b9a5298fb0f.scope Slice=user-1000.slice ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1881312 Title: systemd-run does not make the new scope unit part of the slice specified via the --slice arg Status in systemd: Unknown Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Committed 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=user-1000.slice sleep 1000 Running scope as unit run-r16d872f1b0894b88a79421a890269e6c.scope. ^Z [3]+ Stopped systemd-run --scope --slice=user-1000.slice sleep 1000 root:~# bg [3]+ systemd-run --scope --slice=user-1000.slice sleep 1000 & root:~# systemctl show -p Slice run-r16d872f1b0894b88a79421a890269e6c.scope 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://github.com/systemd/systemd/pull/3094 which is included starting in v230, so is included in Bionic and later. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1881312/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1881312] Re: systemd-run does not make the new scope unit part of the slice specified via the --slice arg
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/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. ** Changed in: systemd (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1881312 Title: systemd-run does not make the new scope unit part of the slice specified via the --slice arg Status in systemd: Unknown Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Committed 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=user-1000.slice sleep 1000 Running scope as unit run-r16d872f1b0894b88a79421a890269e6c.scope. ^Z [3]+ Stopped systemd-run --scope --slice=user-1000.slice sleep 1000 root:~# bg [3]+ systemd-run --scope --slice=user-1000.slice sleep 1000 & root:~# systemctl show -p Slice run-r16d872f1b0894b88a79421a890269e6c.scope 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://github.com/systemd/systemd/pull/3094 which is included starting in v230, so is included in Bionic and later. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1881312/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1881312] Re: systemd-run does not make the new scope unit part of the slice specified via the --slice arg
** Description changed: [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=user-1000.slice sleep 1000 Running scope as unit run-r16d872f1b0894b88a79421a890269e6c.scope. ^Z [3]+ Stopped systemd-run --scope --slice=user-1000.slice sleep 1000 root:~# bg [3]+ systemd-run --scope --slice=user-1000.slice sleep 1000 & root:~# systemctl show -p Slice run-r16d872f1b0894b88a79421a890269e6c.scope Slice=system.slice [regression potential] - TBD + 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://github.com/systemd/systemd/pull/3094 which is included starting in v230, so is included in Bionic and later. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1881312 Title: systemd-run does not make the new scope unit part of the slice specified via the --slice arg Status in systemd: Unknown Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: In Progress 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=user-1000.slice sleep 1000 Running scope as unit run-r16d872f1b0894b88a79421a890269e6c.scope. ^Z [3]+ Stopped systemd-run --scope --slice=user-1000.slice sleep 1000 root:~# bg [3]+ systemd-run --scope --slice=user-1000.slice sleep 1000 & root:~# systemctl show -p Slice run-r16d872f1b0894b88a79421a890269e6c.scope 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://github.com/systemd/systemd/pull/3094 which is included starting in v230, so is included in Bionic and later. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1881312/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp