Bug 1293938

Summary: systemd ships incorrect tmpfiles configuration file
Product: Red Hat Enterprise Linux 7 Reporter: Robert Scheck <redhat-bugzilla>
Component: dracutAssignee: Lukáš Nykrýn <lnykryn>
Status: CLOSED DUPLICATE QA Contact: Release Test Team <release-test-team>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 7.2CC: dracut-maint-list, harald, lnykryn, robert.scheck, systemd-maint-list
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-08-10 12:36:47 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:

Description Robert Scheck 2015-12-23 15:37:08 UTC 
Description of problem:
Dec 23 15:25:49 tux systemd-tmpfiles: Failed to parse ACL "d:group:adm:r-x,d:group:wheel:r-x": Invalid argument. Ignoring
Dec 23 15:25:49 tux systemd-tmpfiles: Failed to parse ACL "group:adm:r-x,group:wheel:r-x": Invalid argument. Ignoring
Dec 23 15:25:49 tux systemd-tmpfiles: Failed to parse ACL "d:group:adm:r-x,d:group:wheel:r-x": Invalid argument. Ignoring
Dec 23 15:25:49 tux systemd-tmpfiles: Failed to parse ACL "group:adm:r-x,group:wheel:r-x": Invalid argument. Ignoring

From my understanding these errors are caused by the original configuration
file shipped via /usr/lib/tmpfiles.d/systemd.conf by RHEL 7.2.

Version-Release number of selected component (if applicable):
systemd-219-19.el7.x86_64

How reproducible:
Everytime after reboot in dmesg(1).

Actual results:
Error messages from systemd-tmpfiles in dmesg(1) after reboot.

Expected results:
No error messages  from systemd-tmpfiles in dmesg(1) after reboot.
Comment 1 Robert Scheck 2015-12-23 15:38:31 UTC 
Cross-filed case 01558854 on the Red Hat customer portal.
Comment 3 Lukáš Nykrýn 2015-12-25 10:32:23 UTC 
https://github.com/haraldh/dracut/commit/1bcb63f97c0168ff91b9d930bb31ad32fb1f2976
Comment 4 Harald Hoyer 2016-08-10 12:36:47 UTC 

*** This bug has been marked as a duplicate of bug 1275792 ***