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 1299652 - Make alua prioritizer able to exclusively use the preferred path, if available
Summary: Make alua prioritizer able to exclusively use the preferred path, if available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: device-mapper-multipath
Version: 7.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Ben Marzinski
QA Contact: Zhang Yi
Milan Navratil
URL:
Whiteboard:
Depends On: 1289353 1305997
Blocks: 1295577 1313485 1364188
TreeView+ depends on / blocked
 
Reported: 2016-01-18 22:01 UTC by Ben Marzinski
Modified: 2021-09-03 11:57 UTC (History)
14 users (show)

Fixed In Version: device-mapper-multipath-0.4.9-87.el7
Doc Type: Release Note
Doc Text:
The "exclusive_pref_bit" optional argument has been added to the *multipath* ALUA prioritizer If the "exclusive_pref_bit" argument is added to the *multipath* Asymmetric Logical Unit Access (ALUA) prioritizer, and a path has the Target Port Group Support (TPGS) `pref` bit set, *multipath* makes a path group using only that path and assigns the highest priority to the path. Users can now either allow the preferred path to be in a path group with other paths that are equally optimized, which is the default option, or in a path group by itself by adding the "exclusive_pref_bit" argument.
Clone Of: 1289353
: 1364188 (view as bug list)
Environment:
Last Closed: 2016-11-04 08:17:04 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2536 0 normal SHIPPED_LIVE device-mapper-multipath bug fix and enhancement update 2016-11-03 14:18:10 UTC

Comment 1 Ben Marzinski 2016-02-26 22:56:11 UTC 
The multipath alua prioritizer now allows a an option, "exclusive_pref_bit"

If you use

    prio "alua exclusive_pref_bit"

in your device configuration, multipath will create a pathgroup that only contains the path with the pref bit set, and will give that pathgroup the highest priority.
Comment 2 Ben Marzinski 2016-03-17 21:23:14 UTC 
Oops. Comment 1 used the RHEL6 syntax.  In RHEL7, you would add

prio_args "exclusive_pref_bit"

to your device configuration. This is only used if you have

prio "alua"

set as well.
Comment 12 errata-xmlrpc 2016-11-04 08:17:04 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://rhn.redhat.com/errata/RHBA-2016-2536.html
Note You need to log in before you can comment on or make changes to this bug.