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 1128254[details]
Sosreport shortly after installation.
Description of problem:
When a system one of the paths of a multipath'ed iSCSI (software!) target is disconnected (e.g. by pulling the network cable) and the system is then rebooted, the system will not recognize the formerly disconnected path when it re-appears.
Version-Release number of selected component (if applicable):
libiscsi-1.9.0-6.el7.x86_64
iscsi-initiator-utils-iscsiuio-6.2.0.873-32.el7.x86_64
iscsi-initiator-utils-6.2.0.873-32.el7.x86_64
How reproducible:
Always
Steps to Reproduce:
1.Configure a system to have duplicate paths to an iSCSI target
2.Install on this iSCSI target, combining the two paths using dm_multipath
3.When the system is up,check the iSCSI and dm_multipath connection, be sure that dm-multipath is working fine, then disconnect one path
4.Reboot, the system should boot properly via the remaining path
5.Reconnect the disconnected path
Actual results:
The system does not even see the re-appearing network connection!
Expected results:
The re-appearing network connection is recognized, an IP address is assigned, the path is added to the multipath'ed device.
Additional info:
Intel Kawela Ports are configured with fixed IP addresses and fixed iSCSI Target Parameters, no DHCP.
I will attach three sosreports:
1) shortly after installation (redundant paths)
2) after reboot with single path
3) after re-enabling formerly missing path
1) What strikes me is that the two interfaces are named "ibft" rather than enp<something>.
2) There is only a single target in /sys/firmware/ibft.
3) There is no information whatsoever present about the fact that the second interface has ever been used to connect to the iSCSI target.
I remember we had issues with iscsi/multipathing before.
Wondering if that has worked at some point so far on rhel7, and if rhel6 deals with the scenario ok. This issue should already be reproducable with a KVM guest, booting a small ipxe cd-imgage in the guest with 2 NICs, using an iscsi target from the linux host.
QA has given me this:
While RHEL6 detects the second path (ethernet[01] and target[01] in /sys/firmware/ibft), dm-multipath does not combine both paths into a single, redundant, drive, neither during installation nor after a boot with both paths active!
So, in essence: no, it did not work on RHEL6, but we would expect it to work.
Created attachment 1128254 [details] Sosreport shortly after installation. Description of problem: When a system one of the paths of a multipath'ed iSCSI (software!) target is disconnected (e.g. by pulling the network cable) and the system is then rebooted, the system will not recognize the formerly disconnected path when it re-appears. Version-Release number of selected component (if applicable): libiscsi-1.9.0-6.el7.x86_64 iscsi-initiator-utils-iscsiuio-6.2.0.873-32.el7.x86_64 iscsi-initiator-utils-6.2.0.873-32.el7.x86_64 How reproducible: Always Steps to Reproduce: 1.Configure a system to have duplicate paths to an iSCSI target 2.Install on this iSCSI target, combining the two paths using dm_multipath 3.When the system is up,check the iSCSI and dm_multipath connection, be sure that dm-multipath is working fine, then disconnect one path 4.Reboot, the system should boot properly via the remaining path 5.Reconnect the disconnected path Actual results: The system does not even see the re-appearing network connection! Expected results: The re-appearing network connection is recognized, an IP address is assigned, the path is added to the multipath'ed device. Additional info: Intel Kawela Ports are configured with fixed IP addresses and fixed iSCSI Target Parameters, no DHCP. I will attach three sosreports: 1) shortly after installation (redundant paths) 2) after reboot with single path 3) after re-enabling formerly missing path