Bug 1324826 - RuntimeDirectory created with wrong group ownership
Summary: RuntimeDirectory created with wrong group ownership
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: systemd
Version: 7.2
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: systemd-maint
QA Contact: Branislav Blaškovič
URL:
Whiteboard:
Depends On:
Blocks: 1289485
TreeView+ depends on / blocked
 
Reported: 2016-04-07 11:36 UTC by Kenneth MacDonald
Modified: 2016-11-04 00:53 UTC (History)
3 users (show)

Fixed In Version: systemd-219-21.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-04 00:53:20 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 Kenneth MacDonald 2016-04-07 11:36:50 UTC
Description of problem:


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

systemd-219-19.el7.x86_64

How reproducible:

Always

Steps to Reproduce:
1. Create a service unit with RuntimeDirectory=, User= and Group= all set
2. Ensure the chosen group is not the primary group of the user
3. Start the service

Actual results:

The /run/service directory is created, but owned by the primary group of the User, not the group defined in the Group= directive in the service unit.

Expected results:

The /run/service directory is created with group set to that defined in the Group= directive in the service unit.

Additional info:

This appears to be the same issue as <https://github.com/systemd/systemd/issues/1231>

Comment 2 Lukáš Nykrýn 2016-04-07 12:10:26 UTC
Looks like we might need to backport https://github.com/systemd/systemd/pull/1320/commits/5bc7452b3219456e07f931e40da30bb94a884293 , but it needs a closer look.

Comment 3 Branislav Blaškovič 2016-04-07 14:44:48 UTC
qa_acking.

Comment 8 errata-xmlrpc 2016-11-04 00:53:20 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.