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 1844577 [details]
create iface logs

Description of problem:
The default iface.net_ifacename is bind to host number causing iSCSI login failure across reboots due to change in host number

Version-Release number of selected component (if applicable):
RHEL 8.5 GA

How reproducible:
100% always

Steps to Reproduce:
1. Configure Marvell Fastlinq iSCSI adapter
2. Load qedi module
3. Create new iface for configuration of the adapter using command 'iscsiadm -m iface'
4. Observe that the default iface.net_ifacename is set to host number
5. Perform discovery and login to iSCSI target
6. Reboot the system and observe that iSCSI login failure
7. The reason being host number has changed across the reboot

Actual results:
iSCSI login failure across system reboots

Expected results:
iSCSI login successful across reboots irrespective of host number change

Additional info:
1. bnx2i iface binds to netdev 
2. Not all iSCSI adapters bind iface to netdev like qedi iface
3. qedi iface does not bind to netdev
4. iface.net_ifacename should not default to host number in case of qedi iface
5. disabling iface.net_ifacename from qedi iface helps resolve the iSCSI target login failures seen across reboots

Chris,
For now we have identified fix in qedi driver to not populate the host_no which is used as value to bind the iface.net_ifacename.
After this change, the net_ifacename will be set to default,
iface.net_ifacename = default

We would post this change to upstream too.
Please suggest if there is anything to take care from open-iscsi point of view. Thanks!

The qedi fix to set net_ifacename to default somehow adds regression to iSCSI target discovery, which means
the host_no is mandatory to be populated by the qedi driver.
Hence for now, we would stick to the workaround of disabling net_ifacename from the iface file.

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.

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days