Bug 1178838
| Summary: | iSCSI multipath fails to work and only succeed after adding configuration values for network using sysctl | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | rhev-integ | ||||
| Component: | vdsm | Assignee: | Maor <mlipchuk> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Elad <ebenahar> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 3.4.0 | CC: | acanan, amureini, asegundo, bazulay, bmarzins, daniel.helgenberger, danken, derez, dornelas, ebenahar, ecohen, ederevea, howey.vernon, iheim, lpeer, lsurette, lvernia, mkalinin, mlipchuk, rhev-integ, schlegel, scohen, tnisan, yeylon, ylavi | ||||
| Target Milestone: | --- | Keywords: | ZStream | ||||
| Target Release: | 3.5.1 | Flags: | ylavi:
Triaged+
|
||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | storage | ||||||
| Fixed In Version: | vdsm-4.16.12-2.el6ev | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | 1112861 | Environment: | |||||
| Last Closed: | 2015-04-28 18:51:16 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | Storage | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | 1112861 | ||||||
| Bug Blocks: | 1140850, 1193058, 1197441 | ||||||
| Attachments: |
|
||||||
|
Comment 1
Dan Kenigsberg
2015-01-05 16:24:04 UTC
Thanks Dan, I guess I was too enthusiastic here and forgot about the VDSM patches. I will add another bug for the engine patch (In reply to Maor from comment #2) > Thanks Dan, > I guess I was too enthusiastic here and forgot about the VDSM patches. > I will add another bug for the engine patch After Amador and I discussed this issue, it seems that it is better not to open a seperate bug on the engine side, and use only this bug for both engine and vdsm patches since they are related for this change Maor, please add steps to reproduce and test so the QA can verify? Reproduce steps: 1. Have a Host with 2 Network Devices both configured for the same subnet 2. Add an iSCSI storage with 2 targets in the same Storage Server. 3. Initialize a Data Center with the Host, an iSCSI Storage and two network interfaces configured 4. Configure an iSCSI bond in the Data Center using those 2 network interfaces 5. Confirmation: Check under /var/lib/iscsi/ that you have two network interfaces which connected to the nodes of the iSCSI 6. Use iptables to block eth2 from the Storage Server Result: Host become Non Operational Expected Result: Host should still be Active Amador, can you please confirm those reproduce steps? Is there any step that is missing or a step that should be rephrased/changed? (In reply to Maor from comment #5) > Reproduce steps: > 1. Have a Host with 2 Network Devices both configured for the same subnet > 2. Add an iSCSI storage with 2 targets in the same Storage Server. > 3. Initialize a Data Center with the Host, an iSCSI Storage and two network > interfaces configured > 4. Configure an iSCSI bond in the Data Center using those 2 network > interfaces > 5. Confirmation: Check under /var/lib/iscsi/ that you have two network > interfaces which connected to the nodes of the iSCSI > 6. Use iptables to block eth2 from the Storage Server Also, unblock eth2, wait the path to recover (multipath -ll) and block eth1. If host is still active, then we are good. > > Result: > Host become Non Operational > > Expected Result: > Host should still be Active > > Amador, can you please confirm those reproduce steps? > Is there any step that is missing or a step that should be rephrased/changed? Created attachment 1000450 [details]
/var/log/messages from verification
iSCSI multipath remains active while one of the paths is blcoked from the host, host remains active.
Failed both the NICs leading to the storage (consecutively, one remained active).
Tested while both the host's NICs and the storage server target located in the same subnet.
Verified using rhev 3.5.1 vt14
/var/log/messages attached
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2015-0904.html |