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.

Bug 1600672

Summary: [BACKPORT] RFE: Make multipath able to blacklist by protocol/transport
Product: Red Hat Enterprise Linux 7 Reporter: Ala Hino <ahino>
Component: device-mapper-multipathAssignee: Ben Marzinski <bmarzins>
Status: CLOSED DUPLICATE QA Contact: Lin Li <lilin>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.5CC: agk, bmarzins, heinzm, lilin, msnitzer, nsoffer, prajnoha, rhandlin, salmy, toneata
Target Milestone: rcKeywords: FutureFeature, ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-07-23 16:48:28 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:
Bug Depends On: 1593459    
Bug Blocks: 1016535    

Description Ala Hino 2018-07-12 18:17:10 UTC
Description of problem:

This bug opened for BZ 1593459 backport purpose.

Right now, there is no way to easily tell multipath that you want to blacklist or whitelist devices based on what protocol and transport method that they are using. You can't easily (for instance) blacklist all devices except scsi devices using Fibre Channel or iSCSI. To solve this multipath needs a new blacklist/blacklist_exceptions type, "protocol". This will allow you to do things like

blacklist {
        protocol ".*"
}

blacklist_exceptions {
        protocol "(scsi:fcp|scsi:iscsi)"

Comment 3 Ben Marzinski 2018-07-13 20:21:37 UTC
This change is largely self-contained, and I'm fine with backporting it.

Comment 4 Ben Marzinski 2018-07-18 02:05:50 UTC
1593459 is the RHEL-7.6 bug. This one is supposed to be a zstream bug. I don't actually know the process to go through to create a zstream bug. So, if requesting the rhel-7.5.z flag, and adding the ZStream flag isn't right way to go about this (I'm pretty sure that PM is supposed to be the ones setting up zstream bugs, so I assume that there is more to it that just this) then I'd like to request a zstream bug. RHEV can provide the business justification, if necessary.