Gianluca, I can see that the workaround you describe here (to complete multipath configuration in CLI) fixes an inconsistency in observed iSCSI sessions. I think it is a shortcoming in oVirt that you had to resort to manual configuration. Could you file a bug about this? Ideally, following the bug template presented to you by Bugzilla, i.e. "Expected: two iSCSI sessions", "Got: one the first node ... one the second node". Edy, Martin, do you think you could help out here? Thanks, Ondra On Fri, Apr 7, 2017 at 5:21 PM, Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
Hello, my configuration is what described here: http://lists.ovirt.org/pipermail/users/2017-March/080992.html
So I'm using iSCSI multipath and not bonding can anyone reproduce?
Initial situation is only one node configured and active with some VMS
I go and configure a second node; it tries to activate but networks are not all already mapped and so gies to non operational. I setup all networks and activate the node
It happens that: - on the first node where I currently have 2 iSCSI connections and 2multipath lines (with p1p1.100 and p1p2) it is instantiated a new iSCSI SID using interface "default" and in multipath -l output I see now 3 lines
- on the newly added node I only see 1 iSCSI SID using interface default
My way to solve the situation was to go inside iscsi multipath section do nothing but save the same config
brutally on first node iscsiadm -m session -u --> all iscsi sessions are closed after a while I see again the original 2 connections recovered, with correct interface names used
- on second node iscsiadm -m session -u --> the only session is cloed nothing happens if I set to maintenance the node and then activate the node --> the 2 correct iscsi sessions are activated...
Thanks Gianluca
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users