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.
Created attachment 1601260[details]
LUN with UUID 3600507681081006e80000000000000d3 has /dev/sdc as path in multipath -ll output while Lun with uuid 600507681081006e8000000000000101 has it as path too in sg_inq -p0x83 /dev/sdc output
Description of problem:
LUN with UUID 3600507681081006e80000000000000d3 has /dev/sdc as path in multipath -ll output while LUN with uuid 600507681081006e8000000000000101 has it as path too in sg_inq -p0x83 /dev/sdc output
Version-Release number of selected component (if applicable):
device-mapper-multipath-0.7.8-7.el8_0.2.x86_64
How reproducible:
100% reproducible
Steps to Reproduce:
1. Map two LUNs from SAN Volume controller cluster, which has two IOgrps
2. Perform NDVM(Non-disruptive volume move) on SVC towards one of the LUNs, please refer to the below link for NDVM operation steps:
https://www.ibm.com/support/knowledgecenter/STVLF4_8.3.0/spectrum.virtualize.830.doc/svc_migratevdiskiogrpscli_42lens.html
3. Perform NDVM on the second LUN
4. The Second LUN will use the faulty path that has been assign to the first LUN, so one physical device (/dev/sdc) will be serving two LUNs with different UUIDs
Actual results:
New path generated will use the faulty path with previously generated device (/dev/sdc)
Thus one device have been used for two LUNs with different UUID
Expected results:
New path generated won't use the previous generated device (/dev/sdc)
Additional info:
In RHEL-8.0 multipathd should be able to detect this and refuse to use the path with a changed UUID. Can you post the multipathd log messages from when you do this test? In RHEL-8.1 multipathd should completely remove and then redo discovery on the path if it notices that the UUID has changed. Would you be able to try this test with the rhel-8.1 beta and post the log messages?
Were you able to capture the logs while reproducing this, or try it on rhel-8.1 beta?
Comment 5RHEL Program Management
2021-02-07 07:29:50 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.