Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Created attachment 1198428[details]
udev debug output from udev-147-2.73.el6_8.1
Description of problem:
udev-147-2.73.el6_8.1 seems to have introduced bug where rules from /etc/udev/rules.d/12-dm-permissions.rules (that set device ownership) stop working. Rolling back "udev" RPM to previous version (udev-147-2.73.el6) fixes the issue.
Version-Release number of selected component (if applicable):
udev-147-2.73.el6_8.1.x86_64
How reproducible:
Always (after installing/upgrading to udev-147-2.73.el6_8.1.x86_64.rpm)
Steps to Reproduce:
1. Update/create /etc/udev/rules.d/12-dm-permission.rules to include rules setting custom ownershipt for specific LV devices. For example:
---
# Udev rules for device-mapper devices.
# For more info see: /usr/share/doc/device-mapper-1.02.53/12-dm-permissions.rules
ACTION!="add|change", GOTO="dm_end"
ENV{DM_UDEV_RULES_VSN}!="?*", GOTO="dm_end"
ENV{DM_VG_NAME}=="vg*", ENV{DM_LV_NAME}=="ifx*", OWNER:="informix", GROUP:="informix", MODE:="660"
LABEL="dm_end"
---
2. Create LV matching the custom rule (/dev/vg01/ifxtest for example)
3. Check permissions of the /dev/dm-?? that got created...
Actual results:
brw-rw----. 1 root disk 253, 38 Sep 6 13:42 /dev/dm-38
Expected results:
brw-rw----. 1 informix informix 253, 38 Sep 6 13:50 /dev/dm-38
Additional info:
Noticeable difference between the old udev versions (that work correctly) and the new version (that does not work correctly), is that old versions logged "set permissions" log entry like this:
Sep 6 13:50:13 qavm21 udevd-work[11467]: set permissions /dev/dm-38, 060660, uid=202, gid=202
While new version doesnt do this anymore (and likely thats why permissions dont get set correctly?).
Attached is log output from udev with the "broken" udev-147-2.73.el6_8.1 and "working" udev-147-2.73.el6, when issuing same command "lvcreate -L 1M -n ifxtest vg01".
Created attachment 1198428 [details] udev debug output from udev-147-2.73.el6_8.1 Description of problem: udev-147-2.73.el6_8.1 seems to have introduced bug where rules from /etc/udev/rules.d/12-dm-permissions.rules (that set device ownership) stop working. Rolling back "udev" RPM to previous version (udev-147-2.73.el6) fixes the issue. Version-Release number of selected component (if applicable): udev-147-2.73.el6_8.1.x86_64 How reproducible: Always (after installing/upgrading to udev-147-2.73.el6_8.1.x86_64.rpm) Steps to Reproduce: 1. Update/create /etc/udev/rules.d/12-dm-permission.rules to include rules setting custom ownershipt for specific LV devices. For example: --- # Udev rules for device-mapper devices. # For more info see: /usr/share/doc/device-mapper-1.02.53/12-dm-permissions.rules ACTION!="add|change", GOTO="dm_end" ENV{DM_UDEV_RULES_VSN}!="?*", GOTO="dm_end" ENV{DM_VG_NAME}=="vg*", ENV{DM_LV_NAME}=="ifx*", OWNER:="informix", GROUP:="informix", MODE:="660" LABEL="dm_end" --- 2. Create LV matching the custom rule (/dev/vg01/ifxtest for example) 3. Check permissions of the /dev/dm-?? that got created... Actual results: brw-rw----. 1 root disk 253, 38 Sep 6 13:42 /dev/dm-38 Expected results: brw-rw----. 1 informix informix 253, 38 Sep 6 13:50 /dev/dm-38 Additional info: Noticeable difference between the old udev versions (that work correctly) and the new version (that does not work correctly), is that old versions logged "set permissions" log entry like this: Sep 6 13:50:13 qavm21 udevd-work[11467]: set permissions /dev/dm-38, 060660, uid=202, gid=202 While new version doesnt do this anymore (and likely thats why permissions dont get set correctly?). Attached is log output from udev with the "broken" udev-147-2.73.el6_8.1 and "working" udev-147-2.73.el6, when issuing same command "lvcreate -L 1M -n ifxtest vg01".