<div dir="ltr"><div><div><div>but VDSM when it starts, it runs command:<br>/usr/sbin/iscsiadm -m node -T iqn.1984-05.com... -I default -p <IP>:3260,1 -l<br></div>and when the above IP address is unavailable (I unpluged array cable for testing HA),<br>it hangs and cannot read vd.conf file,<br></div>so I do not know from where VDSM get above IP addres and why it tires to logon to iSCSI share itself. Because iSCSI daemon does it correctly and do not create sessions where the link is not active.<br><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">2017-03-13 16:15 GMT+01:00 Chris Adams <span dir="ltr"><<a href="mailto:cma@cmadams.net" target="_blank">cma@cmadams.net</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">It's easy enough to verify; just SSH in to the physical machine running<br>
the hosted engine and look. You can see the qemu command line, follow<br>
the links to the block device, then look at the LVM physical volume and<br>
see that it is a multipath device.<br>
<div class="HOEnZb"><div class="h5"><br>
Once upon a time, Marcin Kruk <<a href="mailto:askifyouneed@gmail.com">askifyouneed@gmail.com</a>> said:<br>
> Are you 1000% sure? Because during startup vmsd the comman iscsiadm<br>
> <parameters> <target> is executed, In my opinion vmsd should rely on<br>
> /var/lib/iscsi settings.<br>
><br>
> 2017-03-12 15:02 GMT+01:00 Chris Adams <<a href="mailto:cma@cmadams.net">cma@cmadams.net</a>>:<br>
><br>
> > Once upon a time, Marcin Kruk <<a href="mailto:askifyouneed@gmail.com">askifyouneed@gmail.com</a>> said:<br>
> > > OK, but what your script do, only add paths by the iscsiadm command, but<br>
> > > the question is if hosted-engine can see it.<br>
> > > I do not know how to add an extra path, for example, when I congirured<br>
> > > hosted-engine during installation there was only one path in the target,<br>
> > > but now there are four. So how can I verify how many paths are now, and<br>
> > how<br>
> > > eventually change it.<br>
> ><br>
> > oVirt access iSCSI storage through multipath devices, so adding a path<br>
> > to the multipath device will work. Adding an additional path with<br>
> > iscsiadm causes multipathd to recognize it; you can verify that with<br>
> > "multipath -ll".<br>
> > --<br>
> > Chris Adams <<a href="mailto:cma@cmadams.net">cma@cmadams.net</a>><br>
> > ______________________________<wbr>_________________<br>
> > Users mailing list<br>
> > <a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>
> > <a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/<wbr>mailman/listinfo/users</a><br>
> ><br>
<br>
> ______________________________<wbr>_________________<br>
> Users mailing list<br>
> <a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>
> <a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/<wbr>mailman/listinfo/users</a><br>
<br>
<br>
--<br>
Chris Adams <<a href="mailto:cma@cmadams.net">cma@cmadams.net</a>><br>
______________________________<wbr>_________________<br>
Users mailing list<br>
<a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/<wbr>mailman/listinfo/users</a><br>
</div></div></blockquote></div><br></div>