| Summary: | udev-147-2.73.el6_8.1 ignoring some custom rules (device ownership) | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Timo Kokkonen <tjko> | ||||||
| Component: | udev | Assignee: | Michal Sekletar <msekleta> | ||||||
| Status: | CLOSED DUPLICATE | QA Contact: | qe-baseos-daemons | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 6.8 | CC: | tjko, udev-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: | 2016-09-09 10:22:42 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: | |||||||
| Attachments: |
|
||||||||
Created attachment 1198429 [details]
udev debug output from udev-147-2.73.el6
This is now fixed with udev-147-2.73.el6_8.2. *** This bug has been marked as a duplicate of bug 1371215 *** |
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".