[ovirt-users] ISO not showing in UI
Kyle Bassett
kyle.bassett at ravellosystems.com
Tue Sep 8 21:54:03 UTC 2015
I managed to get this fixed, it was an issues with what user was mounting the nfs.
Thanks for the help, I am doing a detailed blog I will share with other when complete.
Kyle
> On Sep 8, 2015, at 5:02 PM, Alexander Wels <awels at redhat.com> wrote:
>
> On Tuesday, September 08, 2015 04:54:46 PM Kyle Bassett wrote:
>> OK makes sense, I am using a freeness appliance…
>>
>> So I somehow need to create those users? kvm (36)/group vdsm(36) and set
>> that permission to the iso directory?
>>
>> I suspect I wold have to do the same for any other shared storage I plan to
>> use for virtual machines in the cluster?
>>
>> Thanks
>> Kyle
>>
>
> I have never used freenas so I can't help you there, but I am assuming you can
> add users to it using the UI, you just have to make sure the user/group id is
> both 36 (kvm/vdsm) and that the user is able read/write to the appropriate
> exported directories. On the other hand I am wondering how you managed to add
> the data/iso domains if the HVs are unable to connect to it.
>
>>> On Sep 8, 2015, at 4:51 PM, Alexander Wels <awels at redhat.com> wrote:
>>>
>>> On Tuesday, September 08, 2015 04:42:31 PM Kyle Bassett wrote:
>>>> Do I have to do this from the overt-engin or a hypervisor. (when I ssh to
>>>> a
>>>> hv I get the guy menu - not command line).
>>>>
>>>> I ran the iso upload from the engine - I am using a nfs iso repo - not
>>>> local
>>>>
>>>> [root at ovirt-engine-01 /]# engine-iso-uploader list
>>>> Please provide the REST API password for the admin at internal oVirt Engine
>>>> user (CTRL+D to abort): ISO Storage Domain Name | Datacenter
>>>>
>>>> | ISO Domain Status freenas-01-ISO | oVirt-DC-01
>>>> |
>>>> | active
>>>>
>>>> [root at ovirt-engine-01 /]#
>>>>
>>>> I am not sure how to check and set the proper permissions on the nfs/iso
>>>> location.
>>>
>>> Do this on the nfs-server. Basically what happens in the background is
>>> your hv is making a connection to the NFS server as user kvm (36)/group
>>> vdsm(36) in order to obtain the iso information. If the NFS server
>>> doesn't have that user or the permissions to read the directory it will
>>> fail.
>>>
>>> Note that the engine itself doesn't need to be able to connect to the nfs-
>>> server, its the HV (the vdsm process to be exact) that makes the
>>> connection. The engine just tells the vdsm process what it wants done.
>>> This is also why when the engine is down your VMs will be unaffected as
>>> its actually vdsm controlling stuff.
>>>
>>>> Kyle
>>>>
>>>>> On Sep 8, 2015, at 4:39 PM, Alexander Wels <awels at redhat.com
>>>>> <mailto:awels at redhat.com <mailto:awels at redhat.com>>> wrote:>>>
>>>>> On Tuesday, September 08, 2015 04:34:46 PM Kyle Bassett wrote:
>>>>>> Yes, I suspect it may be related to this
>>>>>>
>>>>>> http://www.ovirt.org/Troubleshooting_NFS_Storage_Issues <http://www.ovirt.org/Troubleshooting_NFS_Storage_Issues>
>>>>>> <http://www.ovirt.org/Troubleshooting_NFS_Storage_Issues <http://www.ovirt.org/Troubleshooting_NFS_Storage_Issues>>
>>>>>> <http://www.ovirt.org/Troubleshooting_NFS_Storage_Issues <http://www.ovirt.org/Troubleshooting_NFS_Storage_Issues>
>>>>>> <http://www.ovirt.org/Troubleshooting_NFS_Storage_Issues <http://www.ovirt.org/Troubleshooting_NFS_Storage_Issues>>>
>>>>>> <http://www.ovirt.org/Troubleshooting_NFS_Storage_Issues <http://www.ovirt.org/Troubleshooting_NFS_Storage_Issues>
>>>>>> <http://www.ovirt.org/Troubleshooting_NFS_Storage_Issues <http://www.ovirt.org/Troubleshooting_NFS_Storage_Issues>>
>>>>>> <http://www.ovirt.org/Troubleshooting_NFS_Storage_Issues <http://www.ovirt.org/Troubleshooting_NFS_Storage_Issues>
>>>>>> <http://www.ovirt.org/Troubleshooting_NFS_Storage_Issues <http://www.ovirt.org/Troubleshooting_NFS_Storage_Issues>>>>
>>>>>>
>>>>>> I followed all the instruction to a tee.
>>>>>>
>>>>>> I will try these instructions but this could be a documentation issues
>>>>>> in
>>>>>> the starter guide…
>>>>>>
>>>>>> Kyle
>>>>>
>>>>> In that case I would check to make sure the owner of the file is correct
>>>>> in the actual directory, make sure the files are owned by vdsm/kvm
>>>>> (36/36).
>>>>>
>>>>> Also make sure your export is correct, here is mine for my NFS iso
>>>>> domain:
>>>>> /export/iso
>>>>> *(rw,sync,no_subtree_check,all_squash,anonuid=36,anongid=36)
>>>>>
>>>>>>> On Sep 8, 2015, at 4:31 PM, Alexander Wels <awels at redhat.com <mailto:awels at redhat.com>> wrote:
>>>>>>>
>>>>>>> On Tuesday, September 08, 2015 04:18:07 PM Kyle Bassett wrote:
>>>>>>>> Following the instructions here:
>>>>>>>> http://www.ovirt.org/Quick_Start_Guide <http://www.ovirt.org/Quick_Start_Guide>
>>>>>>>> <http://www.ovirt.org/Quick_Start_Guide <http://www.ovirt.org/Quick_Start_Guide>>
>>>>>>>>
>>>>>>>> I managed to upload an ISO, but it won’t show in the UI - do I need
>>>>>>>> to do
>>>>>>>> something to make it show up? I hit refresh but nothing is showing
>>>>>>>> under
>>>>>>>> this ISO section of the UI
>>>>>>>
>>>>>>> Did you follow step 3?
>>>>>>>
>>>>>>> Storage->select ISO domain->go the images sub tab. That will re-read
>>>>>>> the
>>>>>>> contents of the directory and should show your images.
>>>>>>>
>>>>>>>> I tried it again, and it says it exists from the overt command line…
>>>>>>>>
>>>>>>>>
>>>>>>>> [root at ovirt-engine-01 fedora]# engine-iso-uploader upload -i
>>>>>>>> freenas-01-ISO
>>>>>>>> ubuntu-14.04.3-desktop-amd64.iso Please provide the REST API password
>>>>>>>> for
>>>>>>>> the admin at internal oVirt Engine user (CTRL+D to abort): Uploading,
>>>>>>>> please
>>>>>>>> wait...
>>>>>>>> INFO: Start uploading ubuntu-14.04.3-desktop-amd64.iso
>>>>>>>> ERROR: ubuntu-14.04.3-desktop-amd64.iso exists on 10.0.0.10. Either
>>>>>>>> remove
>>>>>>>> it or supply the --force option to overwrite it.
>>>>>>>> [root at ovirt-engine-01
>>>>>>>> fedora]#
>>>>>>>>
>>>>>>>> Thanks
>>>>>>>> Kyle
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20150908/215a2953/attachment-0001.html>
More information about the Users
mailing list