[Users] Images not appearing in ISO domain

Thu Oct 18 13:42:25 UTC 2012

On 10/18/2012 02:03 AM, Shu Ming wrote:
> I used to have the similar issue that the owner or group of directory 
> became nobody. But I don't have the enviroment to reproduce it now.
Nobody is just an NFS built-in.  I think this generally occurs when the 
UID and GID of the files on the NFS server do not have an analog on the 
client.

In other words, if on the server the files are 1001 and the client 
doesn't have a 1001 the client will see 'nobody'.  There are also all 
sorts of NFS server arguments that you can use to force this condition 
(I beleive).

Cheers,
Keith
>
>
> 2012-10-17 0:16, Neil:
>> On Tue, Oct 16, 2012 at 5:57 PM, Alexandre Santos 
>> <santosam72 at gmail.com> wrote:
>>> 2012/10/16 Neil <nwilson123 at gmail.com>
>>>> On Tue, Oct 16, 2012 at 5:10 PM, Neil <nwilson123 at gmail.com> wrote:
>>>>> On Tue, Oct 16, 2012 at 4:47 PM, Alexandre Santos 
>>>>> <santosam72 at gmail.com>
>>>>> wrote:
>>>>>>
>>>>>> 2012/10/16 Mike Burns <mburns at redhat.com>
>>>>>>> On Tue, 2012-10-16 at 16:33 +0200, Neil wrote:
>>>>>>>> Hi Keith,
>>>>>>>>
>>>>>>>> On Tue, Oct 16, 2012 at 3:48 PM, Keith Robertson
>>>>>>>> <kroberts at redhat.com>
>>>>>>>> wrote:
>>>>>>>>> Neil,
>>>>>>>>>
>>>>>>>>> I suspect that you are having the same issue described in [1].
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> [1] https://bugzilla.redhat.com/show_bug.cgi?id=858880
>>>>>>>> I unfortunately don't have access to view this bug...
>>>>>>>>
>>>>>>>> "You are not authorized to access bug #858880."
>>>>>>>>
>>>>>>>> Is there any progress on repairing it, or do you know if there 
>>>>>>>> is a
>>>>>>>> work round in the meantime?
>>>>>>> You can try going into the nfs share manually and
>>>>>>>
>>>>>>> chown 36:36 *
>>>>>>>
>>>>>>> i.e., if your iso domain is at /export/iso:
>>>>>>>
>>>>>>> chown 36:36 /export/iso/<uuid>/images/<uuid>/*
>>>>>>>
>>>>>>> Note that the uuid is different in both cases above, and for each
>>>>>>> domain.
>>>>>>>
>>>>>>> Not sure if this will help or not, but it's worth a shot.
>>>>>>>
>>>>>>> Mike
>>>>>>>
>>>>>>>> Thanks!
>>>>>>>>
>>>>>>>> Regards.
>>>>>>>>
>>>>>>>> Neil Wilson.
>>>>>>>> _______________________________________________
>>>>>>>> Users mailing list
>>>>>>>> Users at ovirt.org
>>>>>>>> http://lists.ovirt.org/mailman/listinfo/users
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Users mailing list
>>>>>>> Users at ovirt.org
>>>>>>> http://lists.ovirt.org/mailman/listinfo/users
>>>>>>
>>>>>> The owner 36:36 should be vdsm.kvm and not vdsm.vdsm
>>>>>> Do you have a group kvm with gid = 36?
>>>>>>
>>>>>> Alex
>>>>> Hi Alex,
>>>>>
>>>>> I only have a group called vdsm with gid 36...no group kvm.
>>>>>
>>>>> grep 36 /etc/group
>>>>> vdsm:x:36:
>>>>>
>>>>> Same as my user..
>>>>>
>>>>> grep 36 /etc/passwd
>>>>> vdsm:x:36:36::/home/vdsm:/bin/false
>>>>>
>>>>> Thanks
>>>> After messing around with permissions 640 644, 777 and changing
>>>> groups, every time I clicked on the "images" tab my whole storage
>>>> would go offline, so I've now destroyed by old ISO domain and
>>>> re-created it with these exact steps.
>>>>
>>>> Just tried destroying my ISO domain and added a new one, but still the
>>>> images don't show.
>>>>
>>>> mv iso-domain iso-domain-old
>>>> mkdir iso-domain
>>>> chown -R 36:36 iso-domain
>>>> ls -al
>>>> drwxr-xr-x.   3 vdsm vdsm  4096 Oct 16 17:37 iso-domain
>>>>
>>>> In ovirt I went to storages --> NEW domain, and added it as NFS ISO,
>>>> it added, I then activated it and then uploaded a small ISO image, but
>>>> still the image doesn't show.
>>>>
>>>> On my host I ran...
>>>> vdsClient -s 0 getIsoList `vdsClient -s 0 
>>>> getConnectedStoragePoolsList`
>>>> ------ ISO list with proper permissions only -------
>>>>
>>>> I see that on my host the uid and gid of 36 are vdsm:kvm not sure if
>>>> this is somehow related?
>>>>
>>>> This is what I see in my server.log when I click on images now...
>>>> (note that my storage stays online now though since re-creating)
>>>>
>>>> 2012-10-16 17:51:43,596 INFO
>>>> [org.ovirt.engine.core.vdsbroker.irsbroker.IsValidVDSCommand]
>>>> (ajp--0.0.0.0-8009-4) START, IsValidVDSCommand(storagePoolId =
>>>> 2e10a712-16e5-11e2-8e00-fb7c1ec24d65, ignoreFailoverLimit = false,
>>>> compatabilityVersion = null), log id: 5ee36683
>>>> 2012-10-16 17:51:43,599 INFO
>>>> [org.ovirt.engine.core.vdsbroker.irsbroker.IsValidVDSCommand]
>>>> (ajp--0.0.0.0-8009-4) FINISH, IsValidVDSCommand, return: true, log id:
>>>> 5ee36683
>>>> 2012-10-16 17:51:43,602 INFO
>>>> [org.ovirt.engine.core.vdsbroker.irsbroker.GetIsoListVDSCommand]
>>>> (ajp--0.0.0.0-8009-4) START, GetIsoListVDSCommand(storagePoolId =
>>>> 2e10a712-16e5-11e2-8e00-fb7c1ec24d65, ignoreFailoverLimit = false,
>>>> compatabilityVersion = null), log id: e413685
>>>> 2012-10-16 17:51:43,621 INFO
>>>> [org.ovirt.engine.core.vdsbroker.vdsbroker.HsmGetIsoListVDSCommand]
>>>> (ajp--0.0.0.0-8009-4) START, HsmGetIsoListVDSCommand(vdsId =
>>>> 322cbee8-16e6-11e2-9d38-6388c61dd004,
>>>> storagePoolId=2e10a712-16e5-11e2-8e00-fb7c1ec24d65), log id: 19d3e418
>>>> 2012-10-16 17:51:43,678 INFO
>>>> [org.ovirt.engine.core.vdsbroker.vdsbroker.HsmGetIsoListVDSCommand]
>>>> (ajp--0.0.0.0-8009-4) FINISH, HsmGetIsoListVDSCommand, return: [], log
>>>> id: 19d3e418
>>>> 2012-10-16 17:51:43,703 INFO
>>>> [org.ovirt.engine.core.vdsbroker.irsbroker.GetIsoListVDSCommand]
>>>> (ajp--0.0.0.0-8009-4) FINISH, GetIsoListVDSCommand, return: [], log
>>>> id: e413685
>>>> 2012-10-16 17:51:43,802 INFO
>>>> [org.ovirt.engine.core.vdsbroker.irsbroker.IsValidVDSCommand]
>>>> (ajp--0.0.0.0-8009-4) START, IsValidVDSCommand(storagePoolId =
>>>> 2e10a712-16e5-11e2-8e00-fb7c1ec24d65, ignoreFailoverLimit = false,
>>>> compatabilityVersion = null), log id: 2f63dd4f
>>>> 2012-10-16 17:51:43,807 INFO
>>>> [org.ovirt.engine.core.vdsbroker.irsbroker.IsValidVDSCommand]
>>>> (ajp--0.0.0.0-8009-4) FINISH, IsValidVDSCommand, return: true, log id:
>>>> 2f63dd4f
>>>> 2012-10-16 17:51:43,814 INFO
>>>> [org.ovirt.engine.core.vdsbroker.irsbroker.GetFloppyListVDSCommand]
>>>> (ajp--0.0.0.0-8009-4) START, GetFloppyListVDSCommand(storagePoolId =
>>>> 2e10a712-16e5-11e2-8e00-fb7c1ec24d65, ignoreFailoverLimit = false,
>>>> compatabilityVersion = null), log id: 69594af5
>>>> 2012-10-16 17:51:43,839 INFO
>>>> [org.ovirt.engine.core.vdsbroker.irsbroker.GetFloppyListVDSCommand]
>>>> (ajp--0.0.0.0-8009-4) FINISH, GetFloppyListVDSCommand, return: [], log
>>>> id: 69594af5
>>>>
>>>> Not sure what to try next though.
>>>>
>>>> Thanks for all your assistance so far.
>>>>
>>>> Regards.
>>>>
>>>> Neil Wilson.
>>>
>>>
>>> Going to your host console, what do you see on the owner and 
>>> permitions of
>>> the ISO domain? I had a similar issue with a ubuntu server that 
>>> exported the
>>> NFS share as nobody.nobody instead of vdsm.kvm on the host. That 
>>> domain was
>>> activated but I couldn't get to the share with a "permeation denied" 
>>> error"
>> Strangely enough, I see a similar issue...
>>
>> drwxr-xr-x. 3 vdsm nobody 4096 Oct 16 17:37 10.251.193.5:_iso-domain
>>
>> Any ideas how to correct it?
>> _______________________________________________
>> Users mailing list
>> Users at ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>
>