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.

Description of problem:
In RHEL-6.6, if the preferred path bit was set for a path, multipath would create a pathgroup containing only that path. Starting in RHEL-6.7, multipath would also include other paths at the same optimization level.  However, some customers want to use the preferred path to tell multipath that if that path is avilable it should only use that path, not just to make sure that path is in the active pathgroup.

Version-Release number of selected component (if applicable):
device-mapper-multipath-0.4.9-87.el6

How reproducible:
always

Steps to Reproduce:
1. Set ALUA tpg PREF bit on an active/optimized port group in a multipathed array, with other port groups also in the active/optimized state
2. start multipath on the paths from the array
3.

Actual results:
All of the active/optimized paths will be in the multipath's active pathgroup

Expected results:
Only the preferred path will be in multipath's active pathgroup

Additional info:

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.

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-0777.html