Bug 1304597

Summary:	systemd/kmod package update changes permissions of /dev/fuse
Product:	Red Hat Enterprise Linux 7	Reporter:	Travers Carter <tcarter>
Component:	systemd	Assignee:	systemd-maint
Status:	CLOSED WONTFIX	QA Contact:	qe-baseos-daemons
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	7.2	CC:	dwd, systemd-maint-list
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-12-15 07:39:55 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 Travers Carter 2016-02-04 05:32:32 UTC

Description of problem:
After an upgrade to systemd-219-19.el7.x86_64 and kmod-20-5.el7.x86_64

The permissions of /dev/fuse were reset from 0666 to 0600, this appears to be the same symptoms as the systemd upgrade bug in Fedora from a year ago (Redhat BZ 1147248)

I'm not sure whether systemd or kmod is culprit but based on the timestamps in yum.log and the ctime of the device node the problem appears to happen when systemd calls systemd-tmpfiles --create in %post (same as the fedora bug) and applies the permissions from /run/tmpfiles.d/kmod.conf which conflict with those in the udev config


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

How reproducible:
Unsure but I'm seeing it happen on quite a few machines, so I'd guess pretty high

Steps to Reproduce:
1. yum upgrade systemd kmod

Actual results:
$ ls -l /dev/fuse
crw-------. 1 root root 10, 229 Feb  4 15:19 /dev/fuse

Expected results:
$ ls -l /dev/fuse
crw-rw-rw-. 1 root root 10, 229 Feb  1 13:23 /dev/fuse


Additional info:
$ grep fuse /run/tmpfiles.d/* /usr/lib/udev/rules.d/*  | grep 06
/run/tmpfiles.d/kmod.conf:c /dev/fuse 0600 - - - 10:229
/usr/lib/udev/rules.d/50-udev-default.rules:KERNEL=="fuse", MODE="0666", OPTIONS+="static_node=fuse"

Comment 3 Dave Dykstra 2019-04-11 19:18:21 UTC

I encountered a similar symptom in RHEL 7.6.  This ticket is still open, but during my investigation I learned about another bugzilla ticket https://bugzilla.redhat.com/show_bug.cgi?id=1213972 which apparently tracked a fix for RHEL 7.2.  Someone with access to that ticket might want to verify if it is a duplicate.

The problem I noticed in RHEL 7.6 did not happen after a systemd upgrade, but it did happen about 10 minutes after an upgrade of kmod-zfs and corresponded to a time that systemd was creating "Static Device Nodes in /dev...".

Comment 5 RHEL Program Management 2020-12-15 07:39:55 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.