Bug 1370299 - Cannot start a .slice via dbus api StartTransientUnit
Summary: Cannot start a .slice via dbus api StartTransientUnit
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: systemd
Version: 7.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: systemd-maint
QA Contact: Branislav Blaškovič
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-25 20:48 UTC by Derek Carr
Modified: 2016-11-28 10:03 UTC (History)
5 users (show)

Fixed In Version: systemd-219-29.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-04 00:56:32 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2216 0 normal SHIPPED_LIVE systemd bug fix and enhancement update 2016-11-03 13:24:51 UTC

Description Derek Carr 2016-08-25 20:48:19 UTC
Description of problem:

I am unable to use the systemd dbus API to start a slice as a transient unit.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.  Invoke StartTransientUnit with a .slice unit using the dbus API
2.
3.

Actual results:
Unit type slice does not support transient units.

Expected results:
A transient unit of type slice is started.

Additional info:

This appears to be functional in systemd v229, but not in systemd v219 or v222 when tested.  

This feature is needed by OpenShift to support quality of service and pod-level cgroup isolation features.

The commit that appeared to introduce the fix that requires backporting is here:

https://github.com/systemd/systemd/commit/17f62e9bd00f5fefd486475861b06d3ec6b7ee10

From PR:
https://github.com/systemd/systemd/pull/1886

Comment 2 Lukáš Nykrýn 2016-08-30 08:32:11 UTC
Seems to be easy to backport -> devel_ack

Comment 3 Branislav Blaškovič 2016-09-01 11:12:29 UTC
qa acking

Comment 8 errata-xmlrpc 2016-11-04 00:56:32 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-2216.html


Note You need to log in before you can comment on or make changes to this bug.