RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1304597 - systemd/kmod package update changes permissions of /dev/fuse
Summary: systemd/kmod package update changes permissions of /dev/fuse
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: systemd
Version: 7.2
Hardware: Unspecified
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: systemd-maint
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-04 05:32 UTC by Travers Carter
Modified: 2020-12-15 07:39 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-12-15 07:39:55 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

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.
Note You need to log in before you can comment on or make changes to this bug.