Bug 1177345

Summary:	cgred.service
Product:	[Fedora] Fedora	Reporter:	gcarter
Component:	libcgroup	Assignee:	Jan Chaloupka <jchaloup>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	21	CC:	bsingharora, fche, jchaloup, jsafrane, myroslav, varekova
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-01-02 12:42:08 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description gcarter 2014-12-26 11:19:10 UTC

Description of problem:
libcgroup-tools lacks a cgred.service file

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

How reproducible:
yum install libcgroup-tools

Steps to Reproduce:
1. yum install libcgroup-tools
2. systemctl status cgred
3.

Actual results:
systemctl status cgred should return a status, instead service file is not found.

cgredengd binary is also not found anywhere.

Expected results:
should install a cgrules.conf file, cgred.service file, and a cgredengd binary.

Additional info:
Fedora 21 repo contains a broken libcgroup-tools rpm, with incomplete installation of cgroups tools.

Comment 1 Jan Chaloupka 2015-01-02 12:42:08 UTC

In version 0.41, cgred was removed as it is depricated.
Control Group Interface in Systemd is replacement.

http://www.freedesktop.org/wiki/Software/systemd/ControlGroupInterface/

Comment 2 Frank Ch. Eigler 2015-02-18 15:08:01 UTC

Jan, systemd's extensions do not appear to replace all uses of the cgred* capabilities, specifically per-user tasks that are not governed by systemd services.

Comment 3 Jan Chaloupka 2015-02-18 15:09:53 UTC

Hi Frank,

you are right, this is known problem. At the moment we can not do anything about that. We are in the middle of cgred and systemd :(.

Comment 4 Frank Ch. Eigler 2015-02-18 15:57:58 UTC

Do you mean that even if we installed cgred* and activated it only for non-systemd invoked processes/services, it would conflict somehow?

Comment 5 Jan Chaloupka 2015-02-18 16:05:53 UTC

If you use cgred only for non-systemd's cgroups, there woun't be any conflict. Using cgred for systemd's cgroups will lead to an undefined behaviour.