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 1607749 - RFE: Make multipath able to blacklist by protocol/transport [rhel-7.5.z]
Summary: RFE: Make multipath able to blacklist by protocol/transport [rhel-7.5.z]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: device-mapper-multipath
Version: 7.6
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: rc
: ---
Assignee: Ben Marzinski
QA Contact: Lin Li
Marek Suchánek
URL:
Whiteboard:
Depends On: 1593459
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-24 08:00 UTC by Oneata Mircea Teodor
Modified: 2021-09-03 12:06 UTC (History)
12 users (show)

Fixed In Version: device-mapper-multipath-0.4.9-119.el7.1
Doc Type: Enhancement
Doc Text:
Device Mapper Multipath (DM Multipath) now supports the "protocol" configuration option in the "blacklist" and "blacklist_exceptions" configuration sections. This enables you to blacklist or whitelist paths based on the protocol they use, such as "scsi" or "nvme". For SCSI devices, you can also specify the transport: for example "scsi:fcp" or "scsi:iscsi".
Clone Of: 1593459
Environment:
Last Closed: 2018-08-16 14:21:05 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2018:2464 0 None None None 2018-08-16 14:21:12 UTC

Description Oneata Mircea Teodor 2018-07-24 08:00:43 UTC
This bug has been copied from bug #1593459 and has been proposed to be backported to 7.5 z-stream (EUS).

Comment 2 Ben Marzinski 2018-07-24 18:46:09 UTC
Fix backported

Comment 9 errata-xmlrpc 2018-08-16 14:21:05 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2018:2464

Comment 10 Ala Hino 2018-08-27 13:04:11 UTC
Ben,

Please note that in the "Fixed in version" filed, device-mapper-multipath-0.4.9-119.el7.1 is reporter while in comment 6 the following version is reported:

root@storageqe-06 ~]# rpm -qa | grep multipath 
device-mapper-multipath-libs-0.4.9-119.el7_5.1.x86_64
device-mapper-multipath-0.4.9-119.el7_5.1.x86_64

On my host with CentOS 7.5, I see that the version is 0.4.9-119.el7_5.1.x86_64.

Can you please confirm that the version indeed is 0.4.9-119.el7_5.1.x86_64?

Comment 11 Ben Marzinski 2018-08-27 15:07:30 UTC
(In reply to Ala Hino from comment #10)
> Ben,
> 
> Can you please confirm that the version indeed is 0.4.9-119.el7_5.1.x86_64?

That's correct. 0.4.9-119.el7_5.1.x86_64 has the fix.


Note You need to log in before you can comment on or make changes to this bug.