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 887684[details]
log files in /tmp during installation, multipath -ll output ran from a shell, screen shot of multipath tab
Description of problem: FCOE BFS:fcoe:BFS: anaconda multipath would not list more than 2 luns although each mpath has at least 4 luns
Version-Release number of selected component (if applicable):
How reproducible: all the time
This is in FCOE BFS setup where i have 4 intiators connected to target via 4 paths. Each path should have at lest 4 luns
Steps to Reproduce:
1. Start BFS installation
2. Add disk--Add fcoe SAN for ens1f2
3. Repeast step 2 for ens1f3, eno3,eno4
4. Looking at multipath tab, each mpath woult list only 2 luns
5. If i swicth to a shell and run multipath -ll, it list them correspondingly
6.It appears to be anaconda refresh issue.
7.
Actual results: list only 2 luns in mpath
Expected results: should list all luns in the mpath not just 2, could be 4 or more.
Additional info:
Attched log files in /tmp during installation, multipath -ll output ran from a shell, screen shot of multipath tab
Comment 5RHEL Program Management
2020-12-15 07:30:22 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.
Created attachment 887684 [details] log files in /tmp during installation, multipath -ll output ran from a shell, screen shot of multipath tab Description of problem: FCOE BFS:fcoe:BFS: anaconda multipath would not list more than 2 luns although each mpath has at least 4 luns Version-Release number of selected component (if applicable): How reproducible: all the time This is in FCOE BFS setup where i have 4 intiators connected to target via 4 paths. Each path should have at lest 4 luns Steps to Reproduce: 1. Start BFS installation 2. Add disk--Add fcoe SAN for ens1f2 3. Repeast step 2 for ens1f3, eno3,eno4 4. Looking at multipath tab, each mpath woult list only 2 luns 5. If i swicth to a shell and run multipath -ll, it list them correspondingly 6.It appears to be anaconda refresh issue. 7. Actual results: list only 2 luns in mpath Expected results: should list all luns in the mpath not just 2, could be 4 or more. Additional info: Attched log files in /tmp during installation, multipath -ll output ran from a shell, screen shot of multipath tab