Bug 1015515

Summary: Check for DM_UDEV_DISABLE_OTHER_RULES_FLAG instead of DM_UDEV_DISABLE_DISK_RULES_FLAG in 65-md-incremental.rules
Product: Red Hat Enterprise Linux 7 Reporter: Peter Rajnoha <prajnoha>
Component: mdadmAssignee: Jes Sorensen <Jes.Sorensen>
Status: CLOSED CURRENTRELEASE QA Contact: XiaoNi <xni>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 7.0CC: prajnoha
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: mdadm-3.2.6-22.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1015514 Environment:
Last Closed: 2014-06-13 09:42:14 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:
Embargoed:
Attachments:
Description Flags
Check for DM_UDEV_DISABLE_OTHER_RULES_FLAG none

Description Peter Rajnoha 2013-10-04 12:31:14 UTC 
+++ This bug was initially created as a clone of Bug #1015514 +++

There's DM_UDEV_DISABLE_DISK_RULES_FLAG used in /lib/udev/rules.d/65-md-incremental.rules to avoid scanning of inappropriate device-mapper devices. Though this flag should be used only in 13-dm-disk.rules (so this flag is for internal device-mapper's use as these rules belong to device-mapper).

Any external rules should check for DM_UDEV_DISABLE_OTHER_RULES_FLAG for proper coordination with device-mapper devices. Please, see attached patch.
Comment 1 Peter Rajnoha 2013-10-04 12:35:30 UTC 
Created attachment 807608 [details]
Check for DM_UDEV_DISABLE_OTHER_RULES_FLAG
Comment 12 Ludek Smid 2014-06-13 09:42:14 UTC 
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.