Yes, this is what struck me about your situation. Will you be able to find relevant logs regarding multipath configuration, in which we would see when (or even why) the third connection was created on the first node, and only one connection on the second?
On Mon, Apr 10, 2017 at 2:17 PM, Gianluca Cecchi <[email protected]> wrote: > On Mon, Apr 10, 2017 at 2:12 PM, Ondrej Svoboda <[email protected]> > wrote: > >> 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 >> > > Ok, this evening I'm going to open a bugzilla for that. > Please keep in mind that on the already configured node (where before node > addition there were two connections in place with multipath), actually the > node addition generates a third connection, added to the existing two, > using "default" as iSCSI interface (clearly seen if I run "iscsiadm -m > session -P1") .... > > Gianluca > >
_______________________________________________ Users mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/users
