| Summary: | System will not detect redundant path which was down during a reboot | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Josef Möllers <josef.moellers> | ||||||||
| Component: | iscsi-initiator-utils | Assignee: | Chris Leech <cleech> | ||||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Martin Hoyer <mhoyer> | ||||||||
| Severity: | high | Docs Contact: | |||||||||
| Priority: | high | ||||||||||
| Version: | 7.1 | CC: | chorn, mhoyer, rmarigny | ||||||||
| Target Milestone: | rc | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | SA233590760 | ||||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2018-11-01 00:35:00 UTC | Type: | Bug | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Bug Depends On: | |||||||||||
| Bug Blocks: | 1203710, 1245518 | ||||||||||
| Attachments: |
|
||||||||||
Created attachment 1128256 [details]
Sosreport after booting with only a single path
Created attachment 1128257 [details]
Sosreport after re-enabling formerly disconnected path
Added whiteboard and CC chorn. 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 will install RHEL6.7 on the system and try to reproduce. As it is Friday ... stay tuned ;-) Have a nice weekend! 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. As I will be moving on to pastures new in a few weeks time, I will not be able to provide any assistance. So long, Josef Is the issue still observed on RHEL7.3GA? Is the issue still observed on RHEL7.5GA? Likely solved in RHEL7.6GA as part of bz1330865. *** This bug has been marked as a duplicate of bug 1330865 *** |
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