<div dir="ltr">Hi, <div><br></div><div>The storage where 'ISO' storage domain resides has to be reachable for the engine server. Please check network connectivity between the two.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Oct 18, 2017 at 7:41 PM, Alex K <span dir="ltr"><<a href="mailto:rightkicktech@gmail.com" target="_blank">rightkicktech@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div><div>Hi all, <br><br></div>I have setup a self hosted setup with 3 servers with several volumes in replica 3. <br></div>These gluster volumes are set on a separate network (on separate NICs on same servers), dedicated for gluster traffic. The engine does not have any NIC in this network. <br></div>The ISO storage domain is also on top one of these gluster volumes. <br></div><div>Hope this makes sense. <br></div><div><br></div>When I try to upload an ISO file from engine, I get the following error: <br><br>engine-iso-uploader -i ISO upload /usr/share/ovirt-guest-tools-<wbr>iso/oVirt-toolsSetup_4.1-3.<wbr>fc24.iso<br>Please provide the REST API password for the admin@internal oVirt Engine user (CTRL+D to abort): <br>Uploading, please wait...<br>ERROR: mount.nfs: No route to host<br><br></div>Seems that the engine is trying to mount the volume and gives a no route to host. <br><br><div><div>What is the correct procedure to add an ISO domain? Can't ISO domain be on a separate dedicated network which is reachable from each host?</div><div><br></div><div>Thanx, <br></div><div>Alex<br></div><div><div><div><div><div><br></div></div></div></div></div></div></div>
<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></blockquote></div><br></div>