9:46 a.m.
Hi Alex,
Can you check if you have the following on your setup ?
1) gluster volume which will be used as ISO storage domain should have
bricks connected using glusternw.
2) NFS time out is caused due to not having nfs.disable off on the volume.
Can you try to set this and try again.
3) self hosted engine requires an additional NIC on the gluster network for
the engine-iso-uploader to work sucessfully if ovirtmgmt and glusternw are
on a different subnet.
Even after having all the above if things do not work, you can just scp the
file to /mnt/<storage-domain-uuid/>/images/11111111111111-1111-
1111-11111111…/
Hope this helps !!!
Thanks
kasturi
On Thu, Oct 19, 2017 at 1:23 PM, Alex K <rightkicktech(a)gmail.com> wrote:
The only workaround that seems to work for my case is the following:
Enable NFS on ISO gluster volume.
Add ISO volume as NFS using hostname of server on the network that engine
has access.
This is not optimal as HA is not achieve - if I loose that server then I
will need to redefine the ISO domain.
Alex
On Thu, Oct 19, 2017 at 12:09 AM, Alex K <rightkicktech(a)gmail.com> wrote:
> If this is the case then I will try to set the gluster network to be at
> the network that engine can reach prior to adding the ISO domain. I would
> prefere not to add an additional interface to engine as then I will need to
> make the storage network a bridge which might incur some overhead and
> affect performance of storage network.
>
> Alex
>
> On Oct 18, 2017 11:36 PM, "Elad Ben Aharon" <ebenahar(a)redhat.com>
wrote:
>
>> Hi,
>>
>> The storage where 'ISO' storage domain resides has to be reachable for
>> the engine server. Please check network connectivity between the two.
>>
>> On Wed, Oct 18, 2017 at 7:41 PM, Alex K <rightkicktech(a)gmail.com> wrote:
>>
>>> Hi all,
>>>
>>> I have setup a self hosted setup with 3 servers with several volumes in
>>> replica 3.
>>> 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.
>>> The ISO storage domain is also on top one of these gluster volumes.
>>> Hope this makes sense.
>>>
>>> When I try to upload an ISO file from engine, I get the following
>>> error:
>>>
>>> engine-iso-uploader -i ISO upload /usr/share/ovirt-guest-tools-i
>>> so/oVirt-toolsSetup_4.1-3.fc24.iso
>>> Please provide the REST API password for the admin@internal oVirt
>>> Engine user (CTRL+D to abort):
>>> Uploading, please wait...
>>> ERROR: mount.nfs: No route to host
>>>
>>> Seems that the engine is trying to mount the volume and gives a no
>>> route to host.
>>>
>>> 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?
>>>
>>> Thanx,
>>> Alex
>>>
>>>
>>> _______________________________________________
>>> Users mailing list
>>> Users(a)ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/users
>>>
>>>
>>
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users