[Users] Unable to add ISOs to default ISO storage domain

Fri Feb 3 16:34:15 UTC 2012

Can you pin your NFS export to a particular ID (below)? If you do it 
this way it won't matter what ID the client connects as because the NFS 
server will just override it with the one in the exports file.

/virt/iso                      
192.168.122.11(rw,sync,all_squash,anonuid=107,anongid=107)

Cheers,
Keith

On 02/03/2012 11:27 AM, Adam Litke wrote:
> On Fri, Feb 03, 2012 at 09:26:32AM +0000, Andrew Dunlop wrote:
>> It would appear that the problem was the permissions on the files.
>> after I did a chmod 0755 to the .iso it appeared almost immediately in
>> the web admin.
>> Should the iso-uploader script not have changed the permissions of the
>> file? It appears to have set the correct owner.
> Could someone explain why oVirt is even requiring ownership of the iso images by
> a specific user and group?  Isn't it enough to just require read/write
> permissions on the export?  The file ownership requirement is causing us
> problems because we have an NFSv4 storage appliance that refuses to chown files
> to 36:36 because those users are not known to the appliance.
>
>> On 2 February 2012 17:09, Brown, Chris (GE Healthcare)
>> <Christopher.Brown at med.ge.com>  wrote:
>>> Easiest way to go about this, at least the way I go about it... Manually
>>> place your iso images on the NFS ISO share.
>>> This can be accomplished two ways:
>>>
>>> Example 1: If you have direct access to your fileserver EG: NAS/etc and
>>> it is linux based.
>>> Simply login and sftp/scp/NFS/CIFS retrieve and/or copy the images into
>>> /export/path/to/iso/domain/<domUUID/images/11111111-1111-1111-1111-11111
>>> 1111111
>>> Then chown 36:36
>>> /export/path/to/iso/domain/<domUUID/images/11111111-1111-1111-1111-11111
>>> 1111111/*
>>>
>>> Example 2: Mount said NFS mount point on another client and copy the
>>> images into it.
>>> Export on NFS server is for example /rhev/iso -->  mount
>>> <servername_or_ip>:/rhev/iso /mnt
>>> Copy the images into
>>> /mnt/<domUUID/images/11111111-1111-1111-1111-111111111111/
>>> Then chown 36:36
>>> /mnt/<domUUID/images/11111111-1111-1111-1111-111111111111/*
>>>
>>> - Chris
>>>
>>> -----Original Message-----
>>> From: users-bounces at ovirt.org [mailto:users-bounces at ovirt.org] On Behalf
>>> Of Andrew Dunlop
>>> Sent: Thursday, February 02, 2012 10:59 AM
>>> To: users at ovirt.org
>>> Subject: [Users] Unable to add ISOs to default ISO storage domain
>>>
>>> I have been trying to upload ISOs onto my ISO Storage Domain, set up
>>> when I ran engine-setup.
>>> I can run the command and the .iso file is correctly put in place,
>>> however this never appears in the available images for this domain on
>>> the web-admin.
>>> I notice that there are no file entries in
>>> https://xxxx.xxxx.co.uk:8443/api/storagedomains/a677acff-601b-4b6d-86ce-
>>> 0798f3833629/files/
>>> just what is given in the verbose output from the uploader.
>>> Any ideas what the problem might be? I have tried a couple of ISOs and
>>> have also done a cleanup and setup.
>>>
>>> Below is the verbose output from the uploader:
>>>
>>> [admin at xxxx ~]$ sudo engine-iso-uploader -v -f -i ISOs upload
>>> Downloads/TinyCore-current.iso [sudo] password for admin:
>>> Please provide the REST API password for the admin at internal oVirt Engine
>>> user (CTRL+D to abort):
>>> DEBUG: URL is
>>> https://xxxx.xxxx.co.uk:8443/api/storagedomains?search=name%3DISOs
>>> DEBUG: Returned XML is
>>> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
>>> <storage_domains>
>>>     <storage_domain
>>> href="/api/storagedomains/a677acff-601b-4b6d-86ce-0798f3833629"
>>> id="a677acff-601b-4b6d-86ce-0798f3833629">
>>>         <name>ISOs</name>
>>>         <link
>>> href="/api/storagedomains/a677acff-601b-4b6d-86ce-0798f3833629/permissio
>>> ns"
>>> rel="permissions"/>
>>>         <link
>>> href="/api/storagedomains/a677acff-601b-4b6d-86ce-0798f3833629/files"
>>> rel="files"/>
>>>         <type>iso</type>
>>>         <master>false</master>
>>>         <storage>
>>>             <type>nfs</type>srmr
>>>             <address>xxxx.xxxx.co.uk</address>
>>>             <path>/isos</path>
>>>         </storage>users@
>>>         <available>48318382080</available>
>>>         <used>4294967296</used>
>>>         <committed>0</committed>
>>>         <storage_format>v1</storage_format>
>>>     </storage_domain>
>>> </storage_domains>
>>>
>>> DEBUG: id=a677acff-601b-4b6d-86ce-0798f3833629 address=xxxx.xxxx.co.uk
>>> path=/isos
>>> DEBUG: local NFS mount point is /tmp/tmpX03eVj
>>> DEBUG: NFS mount command (/bin/mount -t nfs -o rw,sync,soft
>>> xxxx.xxxx.co.uk:/isos /tmp/tmpX03eVj)
>>> DEBUG: /bin/mount -t nfs -o rw,sync,soft xxxx.xxxx.co.uk:/isos
>>> /tmp/tmpX03eVj
>>> DEBUG: _cmds(['/bin/mount', '-t', 'nfs', '-o', 'rw,sync,soft',
>>> 'xxxx.xxxx.co.uk:/isos', '/tmp/tmpX03eVj'])
>>> DEBUG: returncode(0)
>>> DEBUG: STDOUT()
>>> DEBUG: STDERR()
>>> DEBUG: Size of Downloads/TinyCore-current.iso:  12507136 bytes  12214.0
>>> 1K-blocks       11.0 MB
>>> DEBUG: Available space in
>>> /tmp/tmpX03eVj/a677acff-601b-4b6d-86ce-0798f3833629/images/11111111-1111
>>> -1111-1111-111111111111:        48557457408
>>> bytes   47419392.0 1K-blocks    46308.0 MB
>>> DEBUG: euid(0) egid(0)
>>> DEBUG: euid(0) egid(0)
>>> DEBUG: URL is
>>> https://xxxx.xxxx.co.uk:8443/api/storagedomains/a677acff-601b-4b6d-86ce-
>>> 0798f3833629/files
>>> DEBUG: Returned XML is
>>> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>  <files/>
>>>
>>> DEBUG: /bin/umount -t nfs -f  /tmp/tmpX03eVj
>>> DEBUG: /bin/umount -t nfs -f  /tmp/tmpX03eVj
>>> DEBUG: _cmds(['/bin/umount', '-t', 'nfs', '-f', '/tmp/tmpX03eVj'])
>>> DEBUG: returncode(0)
>>> DEBUG: STDOUT()
>>> DEBUG: STDERR()
>>> _______________________________________________
>>> 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
>>