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.
rhel-8.1 device-mapper-multipath currently has an ANA prioritizer, which is automatically enabled if ANA support is detected on nvme devices. Is there any more work that needs to be done here?
The NVMe Native Multipath support is present in 8.1. It is not the default, however,
the kernel option "nvme_core.multipath=Y" must be used to enable it instead of DM-MP.
It includes the mechanism to read the ANA state and use paths accordingly.
As far as "supported", that really depends upon the storage array vendor qualification.
Different vendors may chose whether to recommend DM-MP or NVMe Native multipath.
We (Red Hat) prefer to offer both alternatives to the customer.
I'm closing this bug, on the grounds that these issues have already been addressed in RHEL-8.1. If I'm missing something, please reopen the bug with an explanation of the outstanding issues.