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. On 2 February 2012 17:09, Brown, Chris (GE Healthcare) <Christopher.Brown@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@ovirt.org [mailto:users-bounces@ovirt.org] On Behalf Of Andrew Dunlop Sent: Thursday, February 02, 2012 10:59 AM To: users@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@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@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@ovirt.org http://lists.ovirt.org/mailman/listinfo/users

Andrew and Chris, You shouldn't need to manually place images on the NFS share and subsequently chmod them. The ISO uploader should be doing both the uploading and the chmod-ing for you, and if it is not doing this then it's a bug. Here is a Successful Example: [root@ovirt ~]# vim keith.iso <-- Create a junk file. [root@ovirt ~]# chmod 400 keith.iso <-- Set restrictive perms on it. [root@ovirt ~]# ovirt-iso-uploader -i iso1 upload keith.iso Please provide the REST API password for RHEV-M (CTRL+D to abort): // Let's check our work... [root@ovirt ~]# mount <ip scrubbed>:/data/ovirt/iso1 /mnt/isodomain/ <-- mount the iso export domain [root@ovirt ~]# su - vdsm -bash-4.1$ ll /mnt/isodomain/92cf90c2-3698-48b5-84fd-d8e4f8684547/images/11111111-1111-1111-1111-111111111111/keith.iso -rw-r-----. 1 vdsm kvm 10 Feb 3 07:45 /mnt/isodomain/92cf90c2-3698-48b5-84fd-d8e4f8684547/images/11111111-1111-1111-1111-111111111111/keith.iso <-- w00t! Andrew, to help me debug, could you... 1. Is your ISO export domain being exported by a *nix system? If so can you reply with the line in /etc/exports that does the exporting. It looks something like mine below... [root@inductor ~]# cat /etc/exports /export *(rw,sync,no_root_squash) 2. Send me the output of "tree -pug" from the iso domain: [root@ovirt ~]# su - vdsm -bash-4.1$ cd /mnt/isodomain/92cf90c2-3698-48b5-84fd-d8e4f8684547/ -bash-4.1$ tree -pug dom_md/ images/ -bash-4.1$ tree -pug images images └── [drwxr-xr-x vdsm kvm ] 11111111-1111-1111-1111-111111111111 <snip> Cheers, Keith On 02/03/2012 05:31 AM, Itamar Heim wrote:

On 02/03/2012 11:26 AM, 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.

Keith ---^ ?

...

On 2 February 2012 17:09, Brown, Chris (GE Healthcare) <Christopher.Brown@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@ovirt.org [mailto:users-bounces@ovirt.org] On Behalf Of Andrew Dunlop Sent: Thursday, February 02, 2012 10:59 AM To: users@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@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@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@ovirt.org http://lists.ovirt.org/mailman/listinfo/users

---

Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users

sorry to jump on the bandwagon here - ive also uploaded an iso to the ISO domain - which i said yes to create it locally on the engine-management host. default exported as /mnt/iso - i didnt have to manually do anything to add it to the domain, only activate it. cat /etc/exports /mnt/iso 0.0.0.0/0.0.0.0(rw) #rhev installer i uploaded my iso like so: /usr/bin/engine-iso-uploader -i ISO -u admin@internal -r ovirtmgr.foo.com:8443 upload os_2.0-784729f4-19.iso It finished successfully, the iso is owned vdsm.kvm and has the default 640 permissions. I tried setting them to 755 as mentioned in one of these threads - but that didnt help.. $ tree -pug /mnt/iso /mnt/iso └── [drwxr-xr-x vdsm kvm ] 23340f35-95ca-4b46-90ec-0c8b83a82786 ├── [drwxr-xr-x vdsm kvm ] dom_md │ ├── [-rw-r--r-- vdsm kvm ] ids │ ├── [-rw-r--r-- vdsm kvm ] inbox │ ├── [-rw-r--r-- vdsm kvm ] leases │ ├── [-rw-r--r-- vdsm kvm ] metadata │ └── [-rw-r--r-- vdsm kvm ] outbox └── [drwxr-xr-x vdsm kvm ] images └── [drwxr-xr-x vdsm kvm ] 11111111-1111-1111-1111-111111111111 └── [-rw-r----- vdsm kvm ] os_2.0-784729f4-19.iso I havent rebooted the ovirtmgr host yet incase that "fixes" it Any ideas? ----- Original Message ----- From: "Keith Robertson" <kroberts@redhat.com> To: "Andrew Dunlop" <ajdunlop@gmail.com>, "Chris Brown (GE Healthcare)" <Christopher.Brown@med.ge.com> Cc: users@ovirt.org Sent: Saturday, 4 February, 2012 1:28:20 AM Subject: Re: [Users] Unable to add ISOs to default ISO storage domain Andrew and Chris, You shouldn't need to manually place images on the NFS share and subsequently chmod them. The ISO uploader should be doing both the uploading and the chmod-ing for you, and if it is not doing this then it's a bug. Here is a Successful Example: [root@ovirt ~]# vim keith.iso <-- Create a junk file. [root@ovirt ~]# chmod 400 keith.iso <-- Set restrictive perms on it. [root@ovirt ~]# ovirt-iso-uploader -i iso1 upload keith.iso Please provide the REST API password for RHEV-M (CTRL+D to abort): // Let's check our work... [root@ovirt ~]# mount <ip scrubbed>:/data/ovirt/iso1 /mnt/isodomain/ <-- mount the iso export domain [root@ovirt ~]# su - vdsm -bash-4.1$ ll /mnt/isodomain/92cf90c2-3698-48b5-84fd-d8e4f8684547/images/11111111-1111-1111-1111-111111111111/keith.iso -rw-r-----. 1 vdsm kvm 10 Feb 3 07:45 /mnt/isodomain/92cf90c2-3698-48b5-84fd-d8e4f8684547/images/11111111-1111-1111-1111-111111111111/keith.iso <-- w00t! Andrew, to help me debug, could you... 1. Is your ISO export domain being exported by a *nix system? If so can you reply with the line in /etc/exports that does the exporting. It looks something like mine below... [root@inductor ~]# cat /etc/exports /export *(rw,sync,no_root_squash) 2. Send me the output of "tree -pug" from the iso domain: [root@ovirt ~]# su - vdsm -bash-4.1$ cd /mnt/isodomain/92cf90c2-3698-48b5-84fd-d8e4f8684547/ -bash-4.1$ tree -pug dom_md/ images/ -bash-4.1$ tree -pug images images └── [drwxr-xr-x vdsm kvm ] 11111111-1111-1111-1111-111111111111 <snip> Cheers, Keith On 02/03/2012 05:31 AM, Itamar Heim wrote:

On 02/03/2012 11:26 AM, 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.

Keith ---^ ?

...

On 2 February 2012 17:09, Brown, Chris (GE Healthcare) <Christopher.Brown@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@ovirt.org [mailto:users-bounces@ovirt.org] On Behalf Of Andrew Dunlop Sent: Thursday, February 02, 2012 10:59 AM To: users@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@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@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@ovirt.org http://lists.ovirt.org/mailman/listinfo/users

---

Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users

_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users

should actually mention - the issue is that i cannot see/select to use it in the webUI - even after logging out and back into it ----- Original Message ----- From: "Spyro Polymiadis" <spyro@rsp.com.au> To: "Keith Robertson" <kroberts@redhat.com> Cc: "Andrew Dunlop" <ajdunlop@gmail.com>, users@ovirt.org Sent: Thursday, 9 February, 2012 2:47:09 PM Subject: Re: [Users] Unable to add ISOs to default ISO storage domain sorry to jump on the bandwagon here - ive also uploaded an iso to the ISO domain - which i said yes to create it locally on the engine-management host. default exported as /mnt/iso - i didnt have to manually do anything to add it to the domain, only activate it. cat /etc/exports /mnt/iso 0.0.0.0/0.0.0.0(rw) #rhev installer i uploaded my iso like so: /usr/bin/engine-iso-uploader -i ISO -u admin@internal -r ovirtmgr.foo.com:8443 upload os_2.0-784729f4-19.iso It finished successfully, the iso is owned vdsm.kvm and has the default 640 permissions. I tried setting them to 755 as mentioned in one of these threads - but that didnt help.. $ tree -pug /mnt/iso /mnt/iso └── [drwxr-xr-x vdsm kvm ] 23340f35-95ca-4b46-90ec-0c8b83a82786 ├── [drwxr-xr-x vdsm kvm ] dom_md │ ├── [-rw-r--r-- vdsm kvm ] ids │ ├── [-rw-r--r-- vdsm kvm ] inbox │ ├── [-rw-r--r-- vdsm kvm ] leases │ ├── [-rw-r--r-- vdsm kvm ] metadata │ └── [-rw-r--r-- vdsm kvm ] outbox └── [drwxr-xr-x vdsm kvm ] images └── [drwxr-xr-x vdsm kvm ] 11111111-1111-1111-1111-111111111111 └── [-rw-r----- vdsm kvm ] os_2.0-784729f4-19.iso I havent rebooted the ovirtmgr host yet incase that "fixes" it Any ideas? ----- Original Message ----- From: "Keith Robertson" <kroberts@redhat.com> To: "Andrew Dunlop" <ajdunlop@gmail.com>, "Chris Brown (GE Healthcare)" <Christopher.Brown@med.ge.com> Cc: users@ovirt.org Sent: Saturday, 4 February, 2012 1:28:20 AM Subject: Re: [Users] Unable to add ISOs to default ISO storage domain Andrew and Chris, You shouldn't need to manually place images on the NFS share and subsequently chmod them. The ISO uploader should be doing both the uploading and the chmod-ing for you, and if it is not doing this then it's a bug. Here is a Successful Example: [root@ovirt ~]# vim keith.iso <-- Create a junk file. [root@ovirt ~]# chmod 400 keith.iso <-- Set restrictive perms on it. [root@ovirt ~]# ovirt-iso-uploader -i iso1 upload keith.iso Please provide the REST API password for RHEV-M (CTRL+D to abort): // Let's check our work... [root@ovirt ~]# mount <ip scrubbed>:/data/ovirt/iso1 /mnt/isodomain/ <-- mount the iso export domain [root@ovirt ~]# su - vdsm -bash-4.1$ ll /mnt/isodomain/92cf90c2-3698-48b5-84fd-d8e4f8684547/images/11111111-1111-1111-1111-111111111111/keith.iso -rw-r-----. 1 vdsm kvm 10 Feb 3 07:45 /mnt/isodomain/92cf90c2-3698-48b5-84fd-d8e4f8684547/images/11111111-1111-1111-1111-111111111111/keith.iso <-- w00t! Andrew, to help me debug, could you... 1. Is your ISO export domain being exported by a *nix system? If so can you reply with the line in /etc/exports that does the exporting. It looks something like mine below... [root@inductor ~]# cat /etc/exports /export *(rw,sync,no_root_squash) 2. Send me the output of "tree -pug" from the iso domain: [root@ovirt ~]# su - vdsm -bash-4.1$ cd /mnt/isodomain/92cf90c2-3698-48b5-84fd-d8e4f8684547/ -bash-4.1$ tree -pug dom_md/ images/ -bash-4.1$ tree -pug images images └── [drwxr-xr-x vdsm kvm ] 11111111-1111-1111-1111-111111111111 <snip> Cheers, Keith On 02/03/2012 05:31 AM, Itamar Heim wrote:

On 02/03/2012 11:26 AM, 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.

Keith ---^ ?

...

On 2 February 2012 17:09, Brown, Chris (GE Healthcare) <Christopher.Brown@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@ovirt.org [mailto:users-bounces@ovirt.org] On Behalf Of Andrew Dunlop Sent: Thursday, February 02, 2012 10:59 AM To: users@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@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@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@ovirt.org http://lists.ovirt.org/mailman/listinfo/users

---

Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users

_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users

Thanks for the info.. the ISO share is attached to the default domain, and is active, and the host (only 1 hypervisor at the moment) is als part of the same domain. The host is up, and it displays SPM on the right hand side the output of vdsClient is interesting... vdsClient -s 0 getIsoList 23340f35-95ca-4b46-90ec-0c8b83a82786 Unknown pool id, pool not connected: ('23340f35-95ca-4b46-90ec-0c8b83a82786',) ----- Original Message ----- From: "Itamar Heim" <iheim@redhat.com> To: "Spyro Polymiadis" <spyro@rsp.com.au> Cc: "Andrew Dunlop" <ajdunlop@gmail.com>, users@ovirt.org Sent: Thursday, 9 February, 2012 5:22:08 PM Subject: Re: [Users] Unable to add ISOs to default ISO storage domain On 02/09/2012 06:18 AM, Spyro Polymiadis wrote:

should actually mention - the issue is that i cannot see/select to use it in the webUI - even after logging out and back into it

1. is the iso domain attached (and activated) to a DC with an active host in it? 2. check the host is up, and is an SPM (right most column in host grid. 3. run the following command on the host vdsClient -s 0 getIsoList 23340f35-95ca-4b46-90ec-0c8b83a82786

----- Original Message ----- From: "Spyro Polymiadis"<spyro@rsp.com.au> To: "Keith Robertson"<kroberts@redhat.com> Cc: "Andrew Dunlop"<ajdunlop@gmail.com>, users@ovirt.org Sent: Thursday, 9 February, 2012 2:47:09 PM Subject: Re: [Users] Unable to add ISOs to default ISO storage domain

sorry to jump on the bandwagon here - ive also uploaded an iso to the ISO domain - which i said yes to create it locally on the engine-management host. default exported as /mnt/iso - i didnt have to manually do anything to add it to the domain, only activate it.

cat /etc/exports /mnt/iso 0.0.0.0/0.0.0.0(rw) #rhev installer

i uploaded my iso like so:

/usr/bin/engine-iso-uploader -i ISO -u admin@internal -r ovirtmgr.foo.com:8443 upload os_2.0-784729f4-19.iso

It finished successfully, the iso is owned vdsm.kvm and has the default 640 permissions. I tried setting them to 755 as mentioned in one of these threads - but that didnt help..

$ tree -pug /mnt/iso

/mnt/iso └── [drwxr-xr-x vdsm kvm ] 23340f35-95ca-4b46-90ec-0c8b83a82786 ├── [drwxr-xr-x vdsm kvm ] dom_md │ ├── [-rw-r--r-- vdsm kvm ] ids │ ├── [-rw-r--r-- vdsm kvm ] inbox │ ├── [-rw-r--r-- vdsm kvm ] leases │ ├── [-rw-r--r-- vdsm kvm ] metadata │ └── [-rw-r--r-- vdsm kvm ] outbox └── [drwxr-xr-x vdsm kvm ] images └── [drwxr-xr-x vdsm kvm ] 11111111-1111-1111-1111-111111111111 └── [-rw-r----- vdsm kvm ] os_2.0-784729f4-19.iso

I havent rebooted the ovirtmgr host yet incase that "fixes" it

Any ideas?

----- Original Message ----- From: "Keith Robertson"<kroberts@redhat.com> To: "Andrew Dunlop"<ajdunlop@gmail.com>, "Chris Brown (GE Healthcare)"<Christopher.Brown@med.ge.com> Cc: users@ovirt.org Sent: Saturday, 4 February, 2012 1:28:20 AM Subject: Re: [Users] Unable to add ISOs to default ISO storage domain

Andrew and Chris,

You shouldn't need to manually place images on the NFS share and subsequently chmod them. The ISO uploader should be doing both the uploading and the chmod-ing for you, and if it is not doing this then it's a bug.

Here is a Successful Example: [root@ovirt ~]# vim keith.iso<-- Create a junk file. [root@ovirt ~]# chmod 400 keith.iso<-- Set restrictive perms on it. [root@ovirt ~]# ovirt-iso-uploader -i iso1 upload keith.iso Please provide the REST API password for RHEV-M (CTRL+D to abort):

// Let's check our work... [root@ovirt ~]# mount<ip scrubbed>:/data/ovirt/iso1 /mnt/isodomain/<-- mount the iso export domain [root@ovirt ~]# su - vdsm -bash-4.1$ ll /mnt/isodomain/92cf90c2-3698-48b5-84fd-d8e4f8684547/images/11111111-1111-1111-1111-111111111111/keith.iso -rw-r-----. 1 vdsm kvm 10 Feb 3 07:45 /mnt/isodomain/92cf90c2-3698-48b5-84fd-d8e4f8684547/images/11111111-1111-1111-1111-111111111111/keith.iso <-- w00t!

Andrew, to help me debug, could you... 1. Is your ISO export domain being exported by a *nix system? If so can you reply with the line in /etc/exports that does the exporting. It looks something like mine below... [root@inductor ~]# cat /etc/exports /export *(rw,sync,no_root_squash)

2. Send me the output of "tree -pug" from the iso domain: [root@ovirt ~]# su - vdsm -bash-4.1$ cd /mnt/isodomain/92cf90c2-3698-48b5-84fd-d8e4f8684547/ -bash-4.1$ tree -pug dom_md/ images/ -bash-4.1$ tree -pug images images └── [drwxr-xr-x vdsm kvm ] 11111111-1111-1111-1111-111111111111 <snip>

Cheers, Keith

On 02/03/2012 05:31 AM, Itamar Heim wrote:

...

On 02/03/2012 11:26 AM, 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.

Keith ---^ ?

...

On 2 February 2012 17:09, Brown, Chris (GE Healthcare) <Christopher.Brown@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@ovirt.org [mailto:users-bounces@ovirt.org] On Behalf Of Andrew Dunlop Sent: Thursday, February 02, 2012 10:59 AM To: users@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@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@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@ovirt.org http://lists.ovirt.org/mailman/listinfo/users

---

Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users

_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users

i have a data domain (NFS Data master) configured for cluster... yes ----- Original Message ----- From: "Itamar Heim" <iheim@redhat.com> To: "Spyro Polymiadis" <spyro@rsp.com.au> Cc: "Andrew Dunlop" <ajdunlop@gmail.com>, users@ovirt.org Sent: Thursday, 9 February, 2012 6:22:02 PM Subject: Re: [Users] Unable to add ISOs to default ISO storage domain On 02/09/2012 09:39 AM, Spyro Polymiadis wrote:

Thanks for the info..

the ISO share is attached to the default domain, and is active, and the host (only 1 hypervisor at the moment) is als part of the same domain. The host is up, and it displays SPM on the right hand side

the output of vdsClient is interesting...

vdsClient -s 0 getIsoList 23340f35-95ca-4b46-90ec-0c8b83a82786 Unknown pool id, pool not connected: ('23340f35-95ca-4b46-90ec-0c8b83a82786',)

did you create a data domain in this data center?

----- Original Message ----- From: "Itamar Heim"<iheim@redhat.com> To: "Spyro Polymiadis"<spyro@rsp.com.au> Cc: "Andrew Dunlop"<ajdunlop@gmail.com>, users@ovirt.org Sent: Thursday, 9 February, 2012 5:22:08 PM Subject: Re: [Users] Unable to add ISOs to default ISO storage domain

On 02/09/2012 06:18 AM, Spyro Polymiadis wrote:

...

should actually mention - the issue is that i cannot see/select to use it in the webUI - even after logging out and back into it

1. is the iso domain attached (and activated) to a DC with an active host in it? 2. check the host is up, and is an SPM (right most column in host grid. 3. run the following command on the host vdsClient -s 0 getIsoList 23340f35-95ca-4b46-90ec-0c8b83a82786

...

----- Original Message ----- From: "Spyro Polymiadis"<spyro@rsp.com.au> To: "Keith Robertson"<kroberts@redhat.com> Cc: "Andrew Dunlop"<ajdunlop@gmail.com>, users@ovirt.org Sent: Thursday, 9 February, 2012 2:47:09 PM Subject: Re: [Users] Unable to add ISOs to default ISO storage domain

sorry to jump on the bandwagon here - ive also uploaded an iso to the ISO domain - which i said yes to create it locally on the engine-management host. default exported as /mnt/iso - i didnt have to manually do anything to add it to the domain, only activate it.

cat /etc/exports /mnt/iso 0.0.0.0/0.0.0.0(rw) #rhev installer

i uploaded my iso like so:

/usr/bin/engine-iso-uploader -i ISO -u admin@internal -r ovirtmgr.foo.com:8443 upload os_2.0-784729f4-19.iso

It finished successfully, the iso is owned vdsm.kvm and has the default 640 permissions. I tried setting them to 755 as mentioned in one of these threads - but that didnt help..

$ tree -pug /mnt/iso

/mnt/iso └── [drwxr-xr-x vdsm kvm ] 23340f35-95ca-4b46-90ec-0c8b83a82786 ├── [drwxr-xr-x vdsm kvm ] dom_md │ ├── [-rw-r--r-- vdsm kvm ] ids │ ├── [-rw-r--r-- vdsm kvm ] inbox │ ├── [-rw-r--r-- vdsm kvm ] leases │ ├── [-rw-r--r-- vdsm kvm ] metadata │ └── [-rw-r--r-- vdsm kvm ] outbox └── [drwxr-xr-x vdsm kvm ] images └── [drwxr-xr-x vdsm kvm ] 11111111-1111-1111-1111-111111111111 └── [-rw-r----- vdsm kvm ] os_2.0-784729f4-19.iso

I havent rebooted the ovirtmgr host yet incase that "fixes" it

To get us some more information please run... rhevm-iso-uploader list -v On 02/09/2012 03:04 AM, Itamar Heim wrote:

On 02/09/2012 09:59 AM, Spyro Polymiadis wrote:

...

i have a data domain (NFS Data master) configured for cluster... yes

and it is active as well at DC level (DC, storage domains)?

...

----- Original Message ----- From: "Itamar Heim"<iheim@redhat.com> To: "Spyro Polymiadis"<spyro@rsp.com.au> Cc: "Andrew Dunlop"<ajdunlop@gmail.com>, users@ovirt.org Sent: Thursday, 9 February, 2012 6:22:02 PM Subject: Re: [Users] Unable to add ISOs to default ISO storage domain

On 02/09/2012 09:39 AM, Spyro Polymiadis wrote:

...

Thanks for the info..

the ISO share is attached to the default domain, and is active, and the host (only 1 hypervisor at the moment) is als part of the same domain. The host is up, and it displays SPM on the right hand side

the output of vdsClient is interesting...

vdsClient -s 0 getIsoList 23340f35-95ca-4b46-90ec-0c8b83a82786 Unknown pool id, pool not connected: ('23340f35-95ca-4b46-90ec-0c8b83a82786',)

did you create a data domain in this data center?

...

----- Original Message ----- From: "Itamar Heim"<iheim@redhat.com> To: "Spyro Polymiadis"<spyro@rsp.com.au> Cc: "Andrew Dunlop"<ajdunlop@gmail.com>, users@ovirt.org Sent: Thursday, 9 February, 2012 5:22:08 PM Subject: Re: [Users] Unable to add ISOs to default ISO storage domain

On 02/09/2012 06:18 AM, Spyro Polymiadis wrote:

...

should actually mention - the issue is that i cannot see/select to use it in the webUI - even after logging out and back into it

1. is the iso domain attached (and activated) to a DC with an active host in it? 2. check the host is up, and is an SPM (right most column in host grid. 3. run the following command on the host vdsClient -s 0 getIsoList 23340f35-95ca-4b46-90ec-0c8b83a82786

...

----- Original Message ----- From: "Spyro Polymiadis"<spyro@rsp.com.au> To: "Keith Robertson"<kroberts@redhat.com> Cc: "Andrew Dunlop"<ajdunlop@gmail.com>, users@ovirt.org Sent: Thursday, 9 February, 2012 2:47:09 PM Subject: Re: [Users] Unable to add ISOs to default ISO storage domain

sorry to jump on the bandwagon here - ive also uploaded an iso to the ISO domain - which i said yes to create it locally on the engine-management host. default exported as /mnt/iso - i didnt have to manually do anything to add it to the domain, only activate it.

cat /etc/exports /mnt/iso 0.0.0.0/0.0.0.0(rw) #rhev installer

i uploaded my iso like so:

/usr/bin/engine-iso-uploader -i ISO -u admin@internal -r ovirtmgr.foo.com:8443 upload os_2.0-784729f4-19.iso

It finished successfully, the iso is owned vdsm.kvm and has the default 640 permissions. I tried setting them to 755 as mentioned in one of these threads - but that didnt help..

$ tree -pug /mnt/iso

/mnt/iso └── [drwxr-xr-x vdsm kvm ] 23340f35-95ca-4b46-90ec-0c8b83a82786 ├── [drwxr-xr-x vdsm kvm ] dom_md │ ├── [-rw-r--r-- vdsm kvm ] ids │ ├── [-rw-r--r-- vdsm kvm ] inbox │ ├── [-rw-r--r-- vdsm kvm ] leases │ ├── [-rw-r--r-- vdsm kvm ] metadata │ └── [-rw-r--r-- vdsm kvm ] outbox └── [drwxr-xr-x vdsm kvm ] images └── [drwxr-xr-x vdsm kvm ] 11111111-1111-1111-1111-111111111111 └── [-rw-r----- vdsm kvm ] os_2.0-784729f4-19.iso

I havent rebooted the ovirtmgr host yet incase that "fixes" it

_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users

Looking at the output, I'm a little curious about the address of the NFS 
server for the ISO domain.  You've got this...
<address>ovirtmgr.foo.com</address>

Can you actually mount that NFS export from your hyper-visor?

Try this...
1. On the hyper-visor do this:
mkdir /mnt/isodir
2. mount ovirtmgr.foo.com:/mnt/iso /mnt/isodir

Does that actually work?

Cheers,
Keith

On 02/09/2012 09:11 AM, Spyro Polymiadis wrote:
> Heres the output mate - cheers :)
>
> DEBUG: URL is https://ovirtmgr.foo.com:8443/api/datacenters
> DEBUG: Returned XML is
> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
> <data_centers>
>      <data_center href="/api/datacenters/bf61bdea-5265-11e1-bd4b-7b05db53545c" id="bf61bdea-5265-11e1-bd4b-7b05db53545c">
>          <name>Default</name>
>          <description>The default Data Center</description>
>          <link href="/api/datacenters/bf61bdea-5265-11e1-bd4b-7b05db53545c/storagedomains" rel="storagedomains"/>
>          <link href="/api/datacenters/bf61bdea-5265-11e1-bd4b-7b05db53545c/permissions" rel="permissions"/>
>          <storage_type>nfs</storage_type>
>          <storage_format>v1</storage_format>
>          <version major="3" minor="0"/>
>          <supported_versions>
>              <version major="3" minor="0"/>
>          </supported_versions>
>          <status>
>              <state>up</state>
>          </status>
>      </data_center>
> </data_centers>
>
> DEBUG: URL is https://ovirtmgr.foo.com:8443/api/datacenters/bf61bdea-5265-11e1-bd4b-7b05db53545c/storagedomains
> DEBUG: Returned XML is
> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
> <storage_domains>
>      <storage_domain href="/api/datacenters/bf61bdea-5265-11e1-bd4b-7b05db53545c/storagedomains/23340f35-95ca-4b46-90ec-0c8b83a82786" id="23340f35-95ca-4b46-90ec-0c8b83a82786">
>          <name>ISO</name>
>          <actions>
>              <link href="/api/datacenters/bf61bdea-5265-11e1-bd4b-7b05db53545c/storagedomains/23340f35-95ca-4b46-90ec-0c8b83a82786/activate" rel="activate"/>
>              <link href="/api/datacenters/bf61bdea-5265-11e1-bd4b-7b05db53545c/storagedomains/23340f35-95ca-4b46-90ec-0c8b83a82786/deactivate" rel="deactivate"/>
>          </actions>
>          <data_center href="/api/datacenters/bf61bdea-5265-11e1-bd4b-7b05db53545c" id="bf61bdea-5265-11e1-bd4b-7b05db53545c"/>
>          <type>iso</type>
>          <status>
>              <state>active</state>
>          </status>
>          <master>false</master>
>          <storage>
>              <type>nfs</type>
>              <address>ovirtmgr.foo.com</address>
>              <path>/mnt/iso</path>
>          </storage>
>          <available>1073741824</available>
>          <used>3221225472</used>
>          <committed>0</committed>
>          <storage_format>v1</storage_format>
>      </storage_domain>
>      <storage_domain href="/api/datacenters/bf61bdea-5265-11e1-bd4b-7b05db53545c/storagedomains/a864b2ed-ecb9-4f7b-be7f-c39e214b868f" id="a864b2ed-ecb9-4f7b-be7f-c39e214b868f">
>          <name>DATASTORE</name>
>          <actions>
>              <link href="/api/datacenters/bf61bdea-5265-11e1-bd4b-7b05db53545c/storagedomains/a864b2ed-ecb9-4f7b-be7f-c39e214b868f/activate" rel="activate"/>
>              <link href="/api/datacenters/bf61bdea-5265-11e1-bd4b-7b05db53545c/storagedomains/a864b2ed-ecb9-4f7b-be7f-c39e214b868f/deactivate" rel="deactivate"/>
>          </actions>
>          <data_center href="/api/datacenters/bf61bdea-5265-11e1-bd4b-7b05db53545c" id="bf61bdea-5265-11e1-bd4b-7b05db53545c"/>
>          <type>data</type>
>          <status>
>              <state>active</state>
>          </status>
>          <master>true</master>
>          <storage>
>              <type>nfs</type>
>              <address>10.250.1.1</address>
>              <path>/VMSTORE/RHEV</path>
>          </storage>
>          <available>5636070834176</available>
>          <used>53743999516672</used>
>          <committed>10737418240</committed>
>          <storage_format>v1</storage_format>
>      </storage_domain>
> </storage_domains>
>
> ISO Storage Domain Name   | Datacenter                | ISO Domain Status
> ISO                       | Default                   | active
>
>
> ----- Original Message -----
> From: "Keith Robertson"<kroberts@redhat.com>
> To: "Spyro Polymiadis"<spyro@rsp.com.au>
> Cc: "Itamar Heim"<iheim@redhat.com>, "Andrew Dunlop"<ajdunlop@gmail.com>, users@ovirt.org
> Sent: Thursday, 9 February, 2012 9:16:19 PM
> Subject: Re: [Users] Unable to add ISOs to default ISO storage domain
>
> To get us some more information please run...
>
> rhevm-iso-uploader list -v
>
> On 02/09/2012 03:04 AM, Itamar Heim wrote:
>> On 02/09/2012 09:59 AM, Spyro Polymiadis wrote:
>>> i have a data domain (NFS Data master) configured for cluster... yes
>> and it is active as well at DC level (DC, storage domains)?
>>
>>> ----- Original Message -----
>>> From: "Itamar Heim"<iheim@redhat.com>
>>> To: "Spyro Polymiadis"<spyro@rsp.com.au>
>>> Cc: "Andrew Dunlop"<ajdunlop@gmail.com>, users@ovirt.org
>>> Sent: Thursday, 9 February, 2012 6:22:02 PM
>>> Subject: Re: [Users] Unable to add ISOs to default ISO storage domain
>>>
>>> On 02/09/2012 09:39 AM, Spyro Polymiadis wrote:
>>>> Thanks for the info..
>>>>
>>>> the ISO share is attached to the default domain, and is active, and
>>>> the host (only 1 hypervisor at the moment) is als part of the same
>>>> domain.
>>>> The host is up, and it displays SPM on the right hand side
>>>>
>>>> the output of vdsClient is interesting...
>>>>
>>>> vdsClient -s 0 getIsoList 23340f35-95ca-4b46-90ec-0c8b83a82786
>>>> Unknown pool id, pool not connected:
>>>> ('23340f35-95ca-4b46-90ec-0c8b83a82786',)
>>> did you create a data domain in this data center?
>>>
>>>>
>>>> ----- Original Message -----
>>>> From: "Itamar Heim"<iheim@redhat.com>
>>>> To: "Spyro Polymiadis"<spyro@rsp.com.au>
>>>> Cc: "Andrew Dunlop"<ajdunlop@gmail.com>, users@ovirt.org
>>>> Sent: Thursday, 9 February, 2012 5:22:08 PM
>>>> Subject: Re: [Users] Unable to add ISOs to default ISO storage domain
>>>>
>>>> On 02/09/2012 06:18 AM, Spyro Polymiadis wrote:
>>>>> should actually mention - the issue is that i cannot see/select to
>>>>> use it in the webUI - even after logging out and back into it
>>>> 1. is the iso domain attached (and activated) to a DC with an active
>>>> host in it?
>>>> 2. check the host is up, and is an SPM (right most column in host grid.
>>>> 3. run the following command on the host
>>>> vdsClient -s 0 getIsoList 23340f35-95ca-4b46-90ec-0c8b83a82786
>>>>
>>>>> ----- Original Message -----
>>>>> From: "Spyro Polymiadis"<spyro@rsp.com.au>
>>>>> To: "Keith Robertson"<kroberts@redhat.com>
>>>>> Cc: "Andrew Dunlop"<ajdunlop@gmail.com>, users@ovirt.org
>>>>> Sent: Thursday, 9 February, 2012 2:47:09 PM
>>>>> Subject: Re: [Users] Unable to add ISOs to default ISO storage domain
>>>>>
>>>>> sorry to jump on the bandwagon here - ive also uploaded an iso to
>>>>> the ISO domain - which i said yes to create it locally on the
>>>>> engine-management host.
>>>>> default exported as /mnt/iso - i didnt have to manually do anything
>>>>> to add it to the domain, only activate it.
>>>>>
>>>>> cat /etc/exports
>>>>> /mnt/iso        0.0.0.0/0.0.0.0(rw)     #rhev installer
>>>>>
>>>>>
>>>>> i uploaded my iso like so:
>>>>>
>>>>>      /usr/bin/engine-iso-uploader -i ISO -u admin@internal -r
>>>>> ovirtmgr.foo.com:8443 upload os_2.0-784729f4-19.iso
>>>>>
>>>>> It finished successfully, the iso is owned vdsm.kvm and has the
>>>>> default 640 permissions.
>>>>> I tried setting them to 755 as mentioned in one of these threads -
>>>>> but that didnt help..
>>>>>
>>>>> $ tree -pug /mnt/iso
>>>>>
>>>>> /mnt/iso
>>>>>         └── [drwxr-xr-x vdsm     kvm     ]
>>>>> 23340f35-95ca-4b46-90ec-0c8b83a82786
>>>>>             ├── [drwxr-xr-x vdsm     kvm     ]  dom_md
>>>>>             │   ├── [-rw-r--r-- vdsm     kvm     ]  ids
>>>>>             │   ├── [-rw-r--r-- vdsm     kvm     ]  inbox
>>>>>             │   ├── [-rw-r--r-- vdsm     kvm     ]  leases
>>>>>             │   ├── [-rw-r--r-- vdsm     kvm     ]  metadata
>>>>>             │   └── [-rw-r--r-- vdsm     kvm     ]  outbox
>>>>>             └── [drwxr-xr-x vdsm     kvm     ]  images
>>>>>                 └── [drwxr-xr-x vdsm     kvm     ]
>>>>> 11111111-1111-1111-1111-111111111111
>>>>>                     └── [-rw-r----- vdsm     kvm     ]
>>>>> os_2.0-784729f4-19.iso
>>>>>
>>>>> I havent rebooted the ovirtmgr host yet incase that "fixes" it
>> _______________________________________________
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users

FYI - i also created a new ISO domain, attached it, uploaded my iso - and it still doesnt appear in the webUI
I also disabled the firewall on both hypervisor and managment servers - but did not make any difference..

does the iso need to be of a specific type? is there some requirement that it must be bootable, or contain an OS, or something else for it not to register?

I still get the message of unknown pool id, pool not connected when i run   vdsClient -s 0 getIsoList fe82b63a-3207-4ce7-a952-ae76a3ef5f24 (with the new pool id)

on the hypervisor, its mounted correctly and i can see the data in /rhev/data-center/mnt/ovirtmgr.foo.com:_mnt_ISO

not sure where to go from here now :(


----- Original Message -----
From: "Spyro Polymiadis" <spyro@rsp.com.au>
To: "Keith Robertson" <kroberts@redhat.com>
Cc: "Itamar Heim" <iheim@redhat.com>, "Andrew Dunlop" <ajdunlop@gmail.com>, users@ovirt.org, "Spyro Polymiadis" <spyro@rsp.com.au>
Sent: Friday, 10 February, 2012 9:25:20 AM
Subject: Re: [Users] Unable to add ISOs to default ISO storage domain

yeppers its a test domain..
the iso path mounts just fine on the hypervisor
;)

----- Original Message -----
From: "Keith Robertson" <kroberts@redhat.com>
To: "Spyro Polymiadis" <spyro@rsp.com.au>
Cc: "Itamar Heim" <iheim@redhat.com>, "Andrew Dunlop" <ajdunlop@gmail.com>, users@ovirt.org
Sent: Friday, 10 February, 2012 1:31:52 AM
Subject: Re: [Users] Unable to add ISOs to default ISO storage domain

Looking at the output, I'm a little curious about the address of the NFS
server for the ISO domain.  You've got this...
<address>ovirtmgr.foo.com</address>

Can you actually mount that NFS export from your hyper-visor?

Try this...
1. On the hyper-visor do this:
mkdir /mnt/isodir
2. mount ovirtmgr.foo.com:/mnt/iso /mnt/isodir

Does that actually work?

Cheers,
Keith

On 02/09/2012 09:11 AM, Spyro Polymiadis wrote:
> Heres the output mate - cheers :)
>
> DEBUG: URL is https://ovirtmgr.foo.com:8443/api/datacenters
> DEBUG: Returned XML is
> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
> <data_centers>
>      <data_center href="/api/datacenters/bf61bdea-5265-11e1-bd4b-7b05db53545c" id="bf61bdea-5265-11e1-bd4b-7b05db53545c">
>          <name>Default</name>
>          <description>The default Data Center</description>
>          <link href="/api/datacenters/bf61bdea-5265-11e1-bd4b-7b05db53545c/storagedomains" rel="storagedomains"/>
>          <link href="/api/datacenters/bf61bdea-5265-11e1-bd4b-7b05db53545c/permissions" rel="permissions"/>
>          <storage_type>nfs</storage_type>
>          <storage_format>v1</storage_format>
>          <version major="3" minor="0"/>
>          <supported_versions>
>              <version major="3" minor="0"/>
>          </supported_versions>
>          <status>
>              <state>up</state>
>          </status>
>      </data_center>
> </data_centers>
>
> DEBUG: URL is https://ovirtmgr.foo.com:8443/api/datacenters/bf61bdea-5265-11e1-bd4b-7b05db53545c/storagedomains
> DEBUG: Returned XML is
> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
> <storage_domains>
>      <storage_domain href="/api/datacenters/bf61bdea-5265-11e1-bd4b-7b05db53545c/storagedomains/23340f35-95ca-4b46-90ec-0c8b83a82786" id="23340f35-95ca-4b46-90ec-0c8b83a82786">
>          <name>ISO</name>
>          <actions>
>              <link href="/api/datacenters/bf61bdea-5265-11e1-bd4b-7b05db53545c/storagedomains/23340f35-95ca-4b46-90ec-0c8b83a82786/activate" rel="activate"/>
>              <link href="/api/datacenters/bf61bdea-5265-11e1-bd4b-7b05db53545c/storagedomains/23340f35-95ca-4b46-90ec-0c8b83a82786/deactivate" rel="deactivate"/>
>          </actions>
>          <data_center href="/api/datacenters/bf61bdea-5265-11e1-bd4b-7b05db53545c" id="bf61bdea-5265-11e1-bd4b-7b05db53545c"/>
>          <type>iso</type>
>          <status>
>              <state>active</state>
>          </status>
>          <master>false</master>
>          <storage>
>              <type>nfs</type>
>              <address>ovirtmgr.foo.com</address>
>              <path>/mnt/iso</path>
>          </storage>
>          <available>1073741824</available>
>          <used>3221225472</used>
>          <committed>0</committed>
>          <storage_format>v1</storage_format>
>      </storage_domain>
>      <storage_domain href="/api/datacenters/bf61bdea-5265-11e1-bd4b-7b05db53545c/storagedomains/a864b2ed-ecb9-4f7b-be7f-c39e214b868f" id="a864b2ed-ecb9-4f7b-be7f-c39e214b868f">
>          <name>DATASTORE</name>
>          <actions>
>              <link href="/api/datacenters/bf61bdea-5265-11e1-bd4b-7b05db53545c/storagedomains/a864b2ed-ecb9-4f7b-be7f-c39e214b868f/activate" rel="activate"/>
>              <link href="/api/datacenters/bf61bdea-5265-11e1-bd4b-7b05db53545c/storagedomains/a864b2ed-ecb9-4f7b-be7f-c39e214b868f/deactivate" rel="deactivate"/>
>          </actions>
>          <data_center href="/api/datacenters/bf61bdea-5265-11e1-bd4b-7b05db53545c" id="bf61bdea-5265-11e1-bd4b-7b05db53545c"/>
>          <type>data</type>
>          <status>
>              <state>active</state>
>          </status>
>          <master>true</master>
>          <storage>
>              <type>nfs</type>
>              <address>10.250.1.1</address>
>              <path>/VMSTORE/RHEV</path>
>          </storage>
>          <available>5636070834176</available>
>          <used>53743999516672</used>
>          <committed>10737418240</committed>
>          <storage_format>v1</storage_format>
>      </storage_domain>
> </storage_domains>
>
> ISO Storage Domain Name   | Datacenter                | ISO Domain Status
> ISO                       | Default                   | active
>
>
> ----- Original Message -----
> From: "Keith Robertson"<kroberts@redhat.com>
> To: "Spyro Polymiadis"<spyro@rsp.com.au>
> Cc: "Itamar Heim"<iheim@redhat.com>, "Andrew Dunlop"<ajdunlop@gmail.com>, users@ovirt.org
> Sent: Thursday, 9 February, 2012 9:16:19 PM
> Subject: Re: [Users] Unable to add ISOs to default ISO storage domain
>
> To get us some more information please run...
>
> rhevm-iso-uploader list -v
>
> On 02/09/2012 03:04 AM, Itamar Heim wrote:
>> On 02/09/2012 09:59 AM, Spyro Polymiadis wrote:
>>> i have a data domain (NFS Data master) configured for cluster... yes
>> and it is active as well at DC level (DC, storage domains)?
>>
>>> ----- Original Message -----
>>> From: "Itamar Heim"<iheim@redhat.com>
>>> To: "Spyro Polymiadis"<spyro@rsp.com.au>
>>> Cc: "Andrew Dunlop"<ajdunlop@gmail.com>, users@ovirt.org
>>> Sent: Thursday, 9 February, 2012 6:22:02 PM
>>> Subject: Re: [Users] Unable to add ISOs to default ISO storage domain
>>>
>>> On 02/09/2012 09:39 AM, Spyro Polymiadis wrote:
>>>> Thanks for the info..
>>>>
>>>> the ISO share is attached to the default domain, and is active, and
>>>> the host (only 1 hypervisor at the moment) is als part of the same
>>>> domain.
>>>> The host is up, and it displays SPM on the right hand side
>>>>
>>>> the output of vdsClient is interesting...
>>>>
>>>> vdsClient -s 0 getIsoList 23340f35-95ca-4b46-90ec-0c8b83a82786
>>>> Unknown pool id, pool not connected:
>>>> ('23340f35-95ca-4b46-90ec-0c8b83a82786',)
>>> did you create a data domain in this data center?
>>>
>>>>
>>>> ----- Original Message -----
>>>> From: "Itamar Heim"<iheim@redhat.com>
>>>> To: "Spyro Polymiadis"<spyro@rsp.com.au>
>>>> Cc: "Andrew Dunlop"<ajdunlop@gmail.com>, users@ovirt.org
>>>> Sent: Thursday, 9 February, 2012 5:22:08 PM
>>>> Subject: Re: [Users] Unable to add ISOs to default ISO storage domain
>>>>
>>>> On 02/09/2012 06:18 AM, Spyro Polymiadis wrote:
>>>>> should actually mention - the issue is that i cannot see/select to
>>>>> use it in the webUI - even after logging out and back into it
>>>> 1. is the iso domain attached (and activated) to a DC with an active
>>>> host in it?
>>>> 2. check the host is up, and is an SPM (right most column in host grid.
>>>> 3. run the following command on the host
>>>> vdsClient -s 0 getIsoList 23340f35-95ca-4b46-90ec-0c8b83a82786
>>>>
>>>>> ----- Original Message -----
>>>>> From: "Spyro Polymiadis"<spyro@rsp.com.au>
>>>>> To: "Keith Robertson"<kroberts@redhat.com>
>>>>> Cc: "Andrew Dunlop"<ajdunlop@gmail.com>, users@ovirt.org
>>>>> Sent: Thursday, 9 February, 2012 2:47:09 PM
>>>>> Subject: Re: [Users] Unable to add ISOs to default ISO storage domain
>>>>>
>>>>> sorry to jump on the bandwagon here - ive also uploaded an iso to
>>>>> the ISO domain - which i said yes to create it locally on the
>>>>> engine-management host.
>>>>> default exported as /mnt/iso - i didnt have to manually do anything
>>>>> to add it to the domain, only activate it.
>>>>>
>>>>> cat /etc/exports
>>>>> /mnt/iso        0.0.0.0/0.0.0.0(rw)     #rhev installer
>>>>>
>>>>>
>>>>> i uploaded my iso like so:
>>>>>
>>>>>      /usr/bin/engine-iso-uploader -i ISO -u admin@internal -r
>>>>> ovirtmgr.foo.com:8443 upload os_2.0-784729f4-19.iso
>>>>>
>>>>> It finished successfully, the iso is owned vdsm.kvm and has the
>>>>> default 640 permissions.
>>>>> I tried setting them to 755 as mentioned in one of these threads -
>>>>> but that didnt help..
>>>>>
>>>>> $ tree -pug /mnt/iso
>>>>>
>>>>> /mnt/iso
>>>>>         └── [drwxr-xr-x vdsm     kvm     ]
>>>>> 23340f35-95ca-4b46-90ec-0c8b83a82786
>>>>>             ├── [drwxr-xr-x vdsm     kvm     ]  dom_md
>>>>>             │   ├── [-rw-r--r-- vdsm     kvm     ]  ids
>>>>>             │   ├── [-rw-r--r-- vdsm     kvm     ]  inbox
>>>>>             │   ├── [-rw-r--r-- vdsm     kvm     ]  leases
>>>>>             │   ├── [-rw-r--r-- vdsm     kvm     ]  metadata
>>>>>             │   └── [-rw-r--r-- vdsm     kvm     ]  outbox
>>>>>             └── [drwxr-xr-x vdsm     kvm     ]  images
>>>>>                 └── [drwxr-xr-x vdsm     kvm     ]
>>>>> 11111111-1111-1111-1111-111111111111
>>>>>                     └── [-rw-r----- vdsm     kvm     ]
>>>>> os_2.0-784729f4-19.iso
>>>>>
>>>>> I havent rebooted the ovirtmgr host yet incase that "fixes" it
>> _______________________________________________
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users

Spyro,

I am also running out of ideas, but I want to verify a few more things 
before I can safely say that there isn't a problem with the NFS ISO domain.

On the hyper-visor, can you..
1. mount ovirtmgr.foo.com:/mnt/iso /mnt/isodir
2. su - vdsm
3. cd 
/mnt/isodir/23340f35-95ca-4b46-90ec-0c8b83a82786/11111111-1111-1111-1111-111111111111
4. ls

Does that work?

Cheers,
Keith


On 02/09/2012 09:59 PM, Spyro Polymiadis wrote:
> FYI - i also created a new ISO domain, attached it, uploaded my iso - and it still doesnt appear in the webUI
> I also disabled the firewall on both hypervisor and managment servers - but did not make any difference..
>
> does the iso need to be of a specific type? is there some requirement that it must be bootable, or contain an OS, or something else for it not to register?
>
> I still get the message of unknown pool id, pool not connected when i run   vdsClient -s 0 getIsoList fe82b63a-3207-4ce7-a952-ae76a3ef5f24 (with the new pool id)
>
> on the hypervisor, its mounted correctly and i can see the data in /rhev/data-center/mnt/ovirtmgr.foo.com:_mnt_ISO
>
> not sure where to go from here now :(
>
>
> ----- Original Message -----
> From: "Spyro Polymiadis"<spyro@rsp.com.au>
> To: "Keith Robertson"<kroberts@redhat.com>
> Cc: "Itamar Heim"<iheim@redhat.com>, "Andrew Dunlop"<ajdunlop@gmail.com>, users@ovirt.org, "Spyro Polymiadis"<spyro@rsp.com.au>
> Sent: Friday, 10 February, 2012 9:25:20 AM
> Subject: Re: [Users] Unable to add ISOs to default ISO storage domain
>
> yeppers its a test domain..
> the iso path mounts just fine on the hypervisor
> ;)
>
> ----- Original Message -----
> From: "Keith Robertson"<kroberts@redhat.com>
> To: "Spyro Polymiadis"<spyro@rsp.com.au>
> Cc: "Itamar Heim"<iheim@redhat.com>, "Andrew Dunlop"<ajdunlop@gmail.com>, users@ovirt.org
> Sent: Friday, 10 February, 2012 1:31:52 AM
> Subject: Re: [Users] Unable to add ISOs to default ISO storage domain
>
> Looking at the output, I'm a little curious about the address of the NFS
> server for the ISO domain.  You've got this...
> <address>ovirtmgr.foo.com</address>
>
> Can you actually mount that NFS export from your hyper-visor?
>
> Try this...
> 1. On the hyper-visor do this:
> mkdir /mnt/isodir
> 2. mount ovirtmgr.foo.com:/mnt/iso /mnt/isodir
>
> Does that actually work?
>
> Cheers,
> Keith
>
> On 02/09/2012 09:11 AM, Spyro Polymiadis wrote:
>> Heres the output mate - cheers :)
>>
>> DEBUG: URL is https://ovirtmgr.foo.com:8443/api/datacenters
>> DEBUG: Returned XML is
>> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
>> <data_centers>
>>       <data_center href="/api/datacenters/bf61bdea-5265-11e1-bd4b-7b05db53545c" id="bf61bdea-5265-11e1-bd4b-7b05db53545c">
>>           <name>Default</name>
>>           <description>The default Data Center</description>
>>           <link href="/api/datacenters/bf61bdea-5265-11e1-bd4b-7b05db53545c/storagedomains" rel="storagedomains"/>
>>           <link href="/api/datacenters/bf61bdea-5265-11e1-bd4b-7b05db53545c/permissions" rel="permissions"/>
>>           <storage_type>nfs</storage_type>
>>           <storage_format>v1</storage_format>
>>           <version major="3" minor="0"/>
>>           <supported_versions>
>>               <version major="3" minor="0"/>
>>           </supported_versions>
>>           <status>
>>               <state>up</state>
>>           </status>
>>       </data_center>
>> </data_centers>
>>
>> DEBUG: URL is https://ovirtmgr.foo.com:8443/api/datacenters/bf61bdea-5265-11e1-bd4b-7b05db53545c/storagedomains
>> DEBUG: Returned XML is
>> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
>> <storage_domains>
>>       <storage_domain href="/api/datacenters/bf61bdea-5265-11e1-bd4b-7b05db53545c/storagedomains/23340f35-95ca-4b46-90ec-0c8b83a82786" id="23340f35-95ca-4b46-90ec-0c8b83a82786">
>>           <name>ISO</name>
>>           <actions>
>>               <link href="/api/datacenters/bf61bdea-5265-11e1-bd4b-7b05db53545c/storagedomains/23340f35-95ca-4b46-90ec-0c8b83a82786/activate" rel="activate"/>
>>               <link href="/api/datacenters/bf61bdea-5265-11e1-bd4b-7b05db53545c/storagedomains/23340f35-95ca-4b46-90ec-0c8b83a82786/deactivate" rel="deactivate"/>
>>           </actions>
>>           <data_center href="/api/datacenters/bf61bdea-5265-11e1-bd4b-7b05db53545c" id="bf61bdea-5265-11e1-bd4b-7b05db53545c"/>
>>           <type>iso</type>
>>           <status>
>>               <state>active</state>
>>           </status>
>>           <master>false</master>
>>           <storage>
>>               <type>nfs</type>
>>               <address>ovirtmgr.foo.com</address>
>>               <path>/mnt/iso</path>
>>           </storage>
>>           <available>1073741824</available>
>>           <used>3221225472</used>
>>           <committed>0</committed>
>>           <storage_format>v1</storage_format>
>>       </storage_domain>
>>       <storage_domain href="/api/datacenters/bf61bdea-5265-11e1-bd4b-7b05db53545c/storagedomains/a864b2ed-ecb9-4f7b-be7f-c39e214b868f" id="a864b2ed-ecb9-4f7b-be7f-c39e214b868f">
>>           <name>DATASTORE</name>
>>           <actions>
>>               <link href="/api/datacenters/bf61bdea-5265-11e1-bd4b-7b05db53545c/storagedomains/a864b2ed-ecb9-4f7b-be7f-c39e214b868f/activate" rel="activate"/>
>>               <link href="/api/datacenters/bf61bdea-5265-11e1-bd4b-7b05db53545c/storagedomains/a864b2ed-ecb9-4f7b-be7f-c39e214b868f/deactivate" rel="deactivate"/>
>>           </actions>
>>           <data_center href="/api/datacenters/bf61bdea-5265-11e1-bd4b-7b05db53545c" id="bf61bdea-5265-11e1-bd4b-7b05db53545c"/>
>>           <type>data</type>
>>           <status>
>>               <state>active</state>
>>           </status>
>>           <master>true</master>
>>           <storage>
>>               <type>nfs</type>
>>               <address>10.250.1.1</address>
>>               <path>/VMSTORE/RHEV</path>
>>           </storage>
>>           <available>5636070834176</available>
>>           <used>53743999516672</used>
>>           <committed>10737418240</committed>
>>           <storage_format>v1</storage_format>
>>       </storage_domain>
>> </storage_domains>
>>
>> ISO Storage Domain Name   | Datacenter                | ISO Domain Status
>> ISO                       | Default                   | active
>>
>>
>> ----- Original Message -----
>> From: "Keith Robertson"<kroberts@redhat.com>
>> To: "Spyro Polymiadis"<spyro@rsp.com.au>
>> Cc: "Itamar Heim"<iheim@redhat.com>, "Andrew Dunlop"<ajdunlop@gmail.com>, users@ovirt.org
>> Sent: Thursday, 9 February, 2012 9:16:19 PM
>> Subject: Re: [Users] Unable to add ISOs to default ISO storage domain
>>
>> To get us some more information please run...
>>
>> rhevm-iso-uploader list -v
>>
>> On 02/09/2012 03:04 AM, Itamar Heim wrote:
>>> On 02/09/2012 09:59 AM, Spyro Polymiadis wrote:
>>>> i have a data domain (NFS Data master) configured for cluster... yes
>>> and it is active as well at DC level (DC, storage domains)?
>>>
>>>> ----- Original Message -----
>>>> From: "Itamar Heim"<iheim@redhat.com>
>>>> To: "Spyro Polymiadis"<spyro@rsp.com.au>
>>>> Cc: "Andrew Dunlop"<ajdunlop@gmail.com>, users@ovirt.org
>>>> Sent: Thursday, 9 February, 2012 6:22:02 PM
>>>> Subject: Re: [Users] Unable to add ISOs to default ISO storage domain
>>>>
>>>> On 02/09/2012 09:39 AM, Spyro Polymiadis wrote:
>>>>> Thanks for the info..
>>>>>
>>>>> the ISO share is attached to the default domain, and is active, and
>>>>> the host (only 1 hypervisor at the moment) is als part of the same
>>>>> domain.
>>>>> The host is up, and it displays SPM on the right hand side
>>>>>
>>>>> the output of vdsClient is interesting...
>>>>>
>>>>> vdsClient -s 0 getIsoList 23340f35-95ca-4b46-90ec-0c8b83a82786
>>>>> Unknown pool id, pool not connected:
>>>>> ('23340f35-95ca-4b46-90ec-0c8b83a82786',)
>>>> did you create a data domain in this data center?
>>>>
>>>>> ----- Original Message -----
>>>>> From: "Itamar Heim"<iheim@redhat.com>
>>>>> To: "Spyro Polymiadis"<spyro@rsp.com.au>
>>>>> Cc: "Andrew Dunlop"<ajdunlop@gmail.com>, users@ovirt.org
>>>>> Sent: Thursday, 9 February, 2012 5:22:08 PM
>>>>> Subject: Re: [Users] Unable to add ISOs to default ISO storage domain
>>>>>
>>>>> On 02/09/2012 06:18 AM, Spyro Polymiadis wrote:
>>>>>> should actually mention - the issue is that i cannot see/select to
>>>>>> use it in the webUI - even after logging out and back into it
>>>>> 1. is the iso domain attached (and activated) to a DC with an active
>>>>> host in it?
>>>>> 2. check the host is up, and is an SPM (right most column in host grid.
>>>>> 3. run the following command on the host
>>>>> vdsClient -s 0 getIsoList 23340f35-95ca-4b46-90ec-0c8b83a82786
>>>>>
>>>>>> ----- Original Message -----
>>>>>> From: "Spyro Polymiadis"<spyro@rsp.com.au>
>>>>>> To: "Keith Robertson"<kroberts@redhat.com>
>>>>>> Cc: "Andrew Dunlop"<ajdunlop@gmail.com>, users@ovirt.org
>>>>>> Sent: Thursday, 9 February, 2012 2:47:09 PM
>>>>>> Subject: Re: [Users] Unable to add ISOs to default ISO storage domain
>>>>>>
>>>>>> sorry to jump on the bandwagon here - ive also uploaded an iso to
>>>>>> the ISO domain - which i said yes to create it locally on the
>>>>>> engine-management host.
>>>>>> default exported as /mnt/iso - i didnt have to manually do anything
>>>>>> to add it to the domain, only activate it.
>>>>>>
>>>>>> cat /etc/exports
>>>>>> /mnt/iso        0.0.0.0/0.0.0.0(rw)     #rhev installer
>>>>>>
>>>>>>
>>>>>> i uploaded my iso like so:
>>>>>>
>>>>>>       /usr/bin/engine-iso-uploader -i ISO -u admin@internal -r
>>>>>> ovirtmgr.foo.com:8443 upload os_2.0-784729f4-19.iso
>>>>>>
>>>>>> It finished successfully, the iso is owned vdsm.kvm and has the
>>>>>> default 640 permissions.
>>>>>> I tried setting them to 755 as mentioned in one of these threads -
>>>>>> but that didnt help..
>>>>>>
>>>>>> $ tree -pug /mnt/iso
>>>>>>
>>>>>> /mnt/iso
>>>>>>          └── [drwxr-xr-x vdsm     kvm     ]
>>>>>> 23340f35-95ca-4b46-90ec-0c8b83a82786
>>>>>>              ├── [drwxr-xr-x vdsm     kvm     ]  dom_md
>>>>>>              │   ├── [-rw-r--r-- vdsm     kvm     ]  ids
>>>>>>              │   ├── [-rw-r--r-- vdsm     kvm     ]  inbox
>>>>>>              │   ├── [-rw-r--r-- vdsm     kvm     ]  leases
>>>>>>              │   ├── [-rw-r--r-- vdsm     kvm     ]  metadata
>>>>>>              │   └── [-rw-r--r-- vdsm     kvm     ]  outbox
>>>>>>              └── [drwxr-xr-x vdsm     kvm     ]  images
>>>>>>                  └── [drwxr-xr-x vdsm     kvm     ]
>>>>>> 11111111-1111-1111-1111-111111111111
>>>>>>                      └── [-rw-r----- vdsm     kvm     ]
>>>>>> os_2.0-784729f4-19.iso
>>>>>>
>>>>>> I havent rebooted the ovirtmgr host yet incase that "fixes" it
>>> _______________________________________________
>>> Users mailing list
>>> Users@ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/users

ok - here we go.. shed some light on the situation...
it looks like the ISO mount is being mounted as user/group nobody on the hypervisor.... 

drwxr-xr-x. 3 nobody nobody 4096 Feb 10 02:52 ovirtmgr.foo.com:_mnt_ISO

This might explain it because the vdsm user cannot read the iso as its mode 640 nobody.nobody...

However on the iso domain host - the permissions are correct.. so the hypervisor isnt mounting the path correctly
Its just on the hypervisor node that its mounting as nobody.nobody... i can mount the iso share to any other linux or mac host, and it mounts with id/guid 36.36 as normal...

I initially thought that the user nobody and group nobody were somehow mapped to id 36, but this isnt the case (its normal, 99)... 

----- Original Message -----
From: "Spyro Polymiadis" <spyro@rsp.com.au>
To: "Keith Robertson" <kroberts@redhat.com>
Cc: "Itamar Heim" <iheim@redhat.com>, "Andrew Dunlop" <ajdunlop@gmail.com>, users@ovirt.org, "Spyro Polymiadis" <spyro@rsp.com.au>
Sent: Saturday, 11 February, 2012 3:59:20 PM
Subject: Re: [Users] Unable to add ISOs to default ISO storage domain

$ mount ovirtmgr.rsp.com.au:/mnt/ISO test/
$ su - vdsm
This account is currently not available.

In /etc/passwd, the account does not have a valid shell... should it have?

vdsm:x:36:36:Node Virtualization Manager:/var/lib/vdsm:/sbin/nologin


----- Original Message -----
From: "Keith Robertson" <kroberts@redhat.com>
To: "Spyro Polymiadis" <spyro@rsp.com.au>
Cc: "Itamar Heim" <iheim@redhat.com>, "Andrew Dunlop" <ajdunlop@gmail.com>, users@ovirt.org
Sent: Friday, 10 February, 2012 11:59:36 PM
Subject: Re: [Users] Unable to add ISOs to default ISO storage domain

Spyro,

I am also running out of ideas, but I want to verify a few more things
before I can safely say that there isn't a problem with the NFS ISO domain.

On the hyper-visor, can you..
1. mount ovirtmgr.foo.com:/mnt/iso /mnt/isodir
2. su - vdsm
3. cd
/mnt/isodir/23340f35-95ca-4b46-90ec-0c8b83a82786/11111111-1111-1111-1111-111111111111
4. ls

Does that work?

Cheers,
Keith


On 02/09/2012 09:59 PM, Spyro Polymiadis wrote:
> FYI - i also created a new ISO domain, attached it, uploaded my iso - and it still doesnt appear in the webUI
> I also disabled the firewall on both hypervisor and managment servers - but did not make any difference..
>
> does the iso need to be of a specific type? is there some requirement that it must be bootable, or contain an OS, or something else for it not to register?
>
> I still get the message of unknown pool id, pool not connected when i run   vdsClient -s 0 getIsoList fe82b63a-3207-4ce7-a952-ae76a3ef5f24 (with the new pool id)
>
> on the hypervisor, its mounted correctly and i can see the data in /rhev/data-center/mnt/ovirtmgr.foo.com:_mnt_ISO
>
> not sure where to go from here now :(
>
>
> ----- Original Message -----
> From: "Spyro Polymiadis"<spyro@rsp.com.au>
> To: "Keith Robertson"<kroberts@redhat.com>
> Cc: "Itamar Heim"<iheim@redhat.com>, "Andrew Dunlop"<ajdunlop@gmail.com>, users@ovirt.org, "Spyro Polymiadis"<spyro@rsp.com.au>
> Sent: Friday, 10 February, 2012 9:25:20 AM
> Subject: Re: [Users] Unable to add ISOs to default ISO storage domain
>
> yeppers its a test domain..
> the iso path mounts just fine on the hypervisor
> ;)
>
> ----- Original Message -----
> From: "Keith Robertson"<kroberts@redhat.com>
> To: "Spyro Polymiadis"<spyro@rsp.com.au>
> Cc: "Itamar Heim"<iheim@redhat.com>, "Andrew Dunlop"<ajdunlop@gmail.com>, users@ovirt.org
> Sent: Friday, 10 February, 2012 1:31:52 AM
> Subject: Re: [Users] Unable to add ISOs to default ISO storage domain
>
> Looking at the output, I'm a little curious about the address of the NFS
> server for the ISO domain.  You've got this...
> <address>ovirtmgr.foo.com</address>
>
> Can you actually mount that NFS export from your hyper-visor?
>
> Try this...
> 1. On the hyper-visor do this:
> mkdir /mnt/isodir
> 2. mount ovirtmgr.foo.com:/mnt/iso /mnt/isodir
>
> Does that actually work?
>
> Cheers,
> Keith
>
> On 02/09/2012 09:11 AM, Spyro Polymiadis wrote:
>> Heres the output mate - cheers :)
>>
>> DEBUG: URL is https://ovirtmgr.foo.com:8443/api/datacenters
>> DEBUG: Returned XML is
>> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
>> <data_centers>
>>       <data_center href="/api/datacenters/bf61bdea-5265-11e1-bd4b-7b05db53545c" id="bf61bdea-5265-11e1-bd4b-7b05db53545c">
>>           <name>Default</name>
>>           <description>The default Data Center</description>
>>           <link href="/api/datacenters/bf61bdea-5265-11e1-bd4b-7b05db53545c/storagedomains" rel="storagedomains"/>
>>           <link href="/api/datacenters/bf61bdea-5265-11e1-bd4b-7b05db53545c/permissions" rel="permissions"/>
>>           <storage_type>nfs</storage_type>
>>           <storage_format>v1</storage_format>
>>           <version major="3" minor="0"/>
>>           <supported_versions>
>>               <version major="3" minor="0"/>
>>           </supported_versions>
>>           <status>
>>               <state>up</state>
>>           </status>
>>       </data_center>
>> </data_centers>
>>
>> DEBUG: URL is https://ovirtmgr.foo.com:8443/api/datacenters/bf61bdea-5265-11e1-bd4b-7b05db53545c/storagedomains
>> DEBUG: Returned XML is
>> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
>> <storage_domains>
>>       <storage_domain href="/api/datacenters/bf61bdea-5265-11e1-bd4b-7b05db53545c/storagedomains/23340f35-95ca-4b46-90ec-0c8b83a82786" id="23340f35-95ca-4b46-90ec-0c8b83a82786">
>>           <name>ISO</name>
>>           <actions>
>>               <link href="/api/datacenters/bf61bdea-5265-11e1-bd4b-7b05db53545c/storagedomains/23340f35-95ca-4b46-90ec-0c8b83a82786/activate" rel="activate"/>
>>               <link href="/api/datacenters/bf61bdea-5265-11e1-bd4b-7b05db53545c/storagedomains/23340f35-95ca-4b46-90ec-0c8b83a82786/deactivate" rel="deactivate"/>
>>           </actions>
>>           <data_center href="/api/datacenters/bf61bdea-5265-11e1-bd4b-7b05db53545c" id="bf61bdea-5265-11e1-bd4b-7b05db53545c"/>
>>           <type>iso</type>
>>           <status>
>>               <state>active</state>
>>           </status>
>>           <master>false</master>
>>           <storage>
>>               <type>nfs</type>
>>               <address>ovirtmgr.foo.com</address>
>>               <path>/mnt/iso</path>
>>           </storage>
>>           <available>1073741824</available>
>>           <used>3221225472</used>
>>           <committed>0</committed>
>>           <storage_format>v1</storage_format>
>>       </storage_domain>
>>       <storage_domain href="/api/datacenters/bf61bdea-5265-11e1-bd4b-7b05db53545c/storagedomains/a864b2ed-ecb9-4f7b-be7f-c39e214b868f" id="a864b2ed-ecb9-4f7b-be7f-c39e214b868f">
>>           <name>DATASTORE</name>
>>           <actions>
>>               <link href="/api/datacenters/bf61bdea-5265-11e1-bd4b-7b05db53545c/storagedomains/a864b2ed-ecb9-4f7b-be7f-c39e214b868f/activate" rel="activate"/>
>>               <link href="/api/datacenters/bf61bdea-5265-11e1-bd4b-7b05db53545c/storagedomains/a864b2ed-ecb9-4f7b-be7f-c39e214b868f/deactivate" rel="deactivate"/>
>>           </actions>
>>           <data_center href="/api/datacenters/bf61bdea-5265-11e1-bd4b-7b05db53545c" id="bf61bdea-5265-11e1-bd4b-7b05db53545c"/>
>>           <type>data</type>
>>           <status>
>>               <state>active</state>
>>           </status>
>>           <master>true</master>
>>           <storage>
>>               <type>nfs</type>
>>               <address>10.250.1.1</address>
>>               <path>/VMSTORE/RHEV</path>
>>           </storage>
>>           <available>5636070834176</available>
>>           <used>53743999516672</used>
>>           <committed>10737418240</committed>
>>           <storage_format>v1</storage_format>
>>       </storage_domain>
>> </storage_domains>
>>
>> ISO Storage Domain Name   | Datacenter                | ISO Domain Status
>> ISO                       | Default                   | active
>>
>>
>> ----- Original Message -----
>> From: "Keith Robertson"<kroberts@redhat.com>
>> To: "Spyro Polymiadis"<spyro@rsp.com.au>
>> Cc: "Itamar Heim"<iheim@redhat.com>, "Andrew Dunlop"<ajdunlop@gmail.com>, users@ovirt.org
>> Sent: Thursday, 9 February, 2012 9:16:19 PM
>> Subject: Re: [Users] Unable to add ISOs to default ISO storage domain
>>
>> To get us some more information please run...
>>
>> rhevm-iso-uploader list -v
>>
>> On 02/09/2012 03:04 AM, Itamar Heim wrote:
>>> On 02/09/2012 09:59 AM, Spyro Polymiadis wrote:
>>>> i have a data domain (NFS Data master) configured for cluster... yes
>>> and it is active as well at DC level (DC, storage domains)?
>>>
>>>> ----- Original Message -----
>>>> From: "Itamar Heim"<iheim@redhat.com>
>>>> To: "Spyro Polymiadis"<spyro@rsp.com.au>
>>>> Cc: "Andrew Dunlop"<ajdunlop@gmail.com>, users@ovirt.org
>>>> Sent: Thursday, 9 February, 2012 6:22:02 PM
>>>> Subject: Re: [Users] Unable to add ISOs to default ISO storage domain
>>>>
>>>> On 02/09/2012 09:39 AM, Spyro Polymiadis wrote:
>>>>> Thanks for the info..
>>>>>
>>>>> the ISO share is attached to the default domain, and is active, and
>>>>> the host (only 1 hypervisor at the moment) is als part of the same
>>>>> domain.
>>>>> The host is up, and it displays SPM on the right hand side
>>>>>
>>>>> the output of vdsClient is interesting...
>>>>>
>>>>> vdsClient -s 0 getIsoList 23340f35-95ca-4b46-90ec-0c8b83a82786
>>>>> Unknown pool id, pool not connected:
>>>>> ('23340f35-95ca-4b46-90ec-0c8b83a82786',)
>>>> did you create a data domain in this data center?
>>>>
>>>>> ----- Original Message -----
>>>>> From: "Itamar Heim"<iheim@redhat.com>
>>>>> To: "Spyro Polymiadis"<spyro@rsp.com.au>
>>>>> Cc: "Andrew Dunlop"<ajdunlop@gmail.com>, users@ovirt.org
>>>>> Sent: Thursday, 9 February, 2012 5:22:08 PM
>>>>> Subject: Re: [Users] Unable to add ISOs to default ISO storage domain
>>>>>
>>>>> On 02/09/2012 06:18 AM, Spyro Polymiadis wrote:
>>>>>> should actually mention - the issue is that i cannot see/select to
>>>>>> use it in the webUI - even after logging out and back into it
>>>>> 1. is the iso domain attached (and activated) to a DC with an active
>>>>> host in it?
>>>>> 2. check the host is up, and is an SPM (right most column in host grid.
>>>>> 3. run the following command on the host
>>>>> vdsClient -s 0 getIsoList 23340f35-95ca-4b46-90ec-0c8b83a82786
>>>>>
>>>>>> ----- Original Message -----
>>>>>> From: "Spyro Polymiadis"<spyro@rsp.com.au>
>>>>>> To: "Keith Robertson"<kroberts@redhat.com>
>>>>>> Cc: "Andrew Dunlop"<ajdunlop@gmail.com>, users@ovirt.org
>>>>>> Sent: Thursday, 9 February, 2012 2:47:09 PM
>>>>>> Subject: Re: [Users] Unable to add ISOs to default ISO storage domain
>>>>>>
>>>>>> sorry to jump on the bandwagon here - ive also uploaded an iso to
>>>>>> the ISO domain - which i said yes to create it locally on the
>>>>>> engine-management host.
>>>>>> default exported as /mnt/iso - i didnt have to manually do anything
>>>>>> to add it to the domain, only activate it.
>>>>>>
>>>>>> cat /etc/exports
>>>>>> /mnt/iso        0.0.0.0/0.0.0.0(rw)     #rhev installer
>>>>>>
>>>>>>
>>>>>> i uploaded my iso like so:
>>>>>>
>>>>>>       /usr/bin/engine-iso-uploader -i ISO -u admin@internal -r
>>>>>> ovirtmgr.foo.com:8443 upload os_2.0-784729f4-19.iso
>>>>>>
>>>>>> It finished successfully, the iso is owned vdsm.kvm and has the
>>>>>> default 640 permissions.
>>>>>> I tried setting them to 755 as mentioned in one of these threads -
>>>>>> but that didnt help..
>>>>>>
>>>>>> $ tree -pug /mnt/iso
>>>>>>
>>>>>> /mnt/iso
>>>>>>          └── [drwxr-xr-x vdsm     kvm     ]
>>>>>> 23340f35-95ca-4b46-90ec-0c8b83a82786
>>>>>>              ├── [drwxr-xr-x vdsm     kvm     ]  dom_md
>>>>>>              │   ├── [-rw-r--r-- vdsm     kvm     ]  ids
>>>>>>              │   ├── [-rw-r--r-- vdsm     kvm     ]  inbox
>>>>>>              │   ├── [-rw-r--r-- vdsm     kvm     ]  leases
>>>>>>              │   ├── [-rw-r--r-- vdsm     kvm     ]  metadata
>>>>>>              │   └── [-rw-r--r-- vdsm     kvm     ]  outbox
>>>>>>              └── [drwxr-xr-x vdsm     kvm     ]  images
>>>>>>                  └── [drwxr-xr-x vdsm     kvm     ]
>>>>>> 11111111-1111-1111-1111-111111111111
>>>>>>                      └── [-rw-r----- vdsm     kvm     ]
>>>>>> os_2.0-784729f4-19.iso
>>>>>>
>>>>>> I havent rebooted the ovirtmgr host yet incase that "fixes" it
>>> _______________________________________________
>>> Users mailing list
>>> Users@ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/users

lol that first paragraph didnt make any sence... was supposed to read

"I decided to try and re-mount the ISO domain using mount -o vers=3 ovirtmgr.foo.com:/mnt/ISO /rhev/data-centre/mnt/ovirtmgr.foo.com:_mnt/ISO and the mount was correctly mounted with vdsm.kvm permissions and then immediately the ISO appeared in the webUI..."


----- Original Message -----
From: "Spyro Polymiadis" <spyro@rsp.com.au>
To: "Spyro Polymiadis" <spyro@rsp.com.au>
Cc: "Itamar Heim" <iheim@redhat.com>, "Andrew Dunlop" <ajdunlop@gmail.com>, users@ovirt.org, "Keith Robertson" <kroberts@redhat.com>
Sent: Saturday, 11 February, 2012 5:46:53 PM
Subject: SOLVED: Re: [Users] Unable to add ISOs to default ISO storage domain

Turns out the problem is something to do with using NFSv4....
looking off the back of this thread https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/662711
I decided to try and re-mount the ISO domain user /rhev/data-centre/mnt/ovirtmgr.foo.com:_mnt/ISO
and immediately the ISO appeared in the webUI...

So, looks like the ovirtmgr host, needs to only use nfsv3, so the client does not try and negotiate v4 first...
i was able to force "no v4" on the ovirtmgr host, by adding

RPCNFSDARGS="-N 4"

to  /etc/sysconfig/nfs, then restarting NFS server, systemctl restart nfs-server.service

Then i remounted the ISO domain on the hypervisor, and it just worked.

So the problem is, NFSv4 server with NFSv4 client = issues.... which make sence, as all the other hosts i used to mount the export, was an nfs3 client only...

Thanks for everyone for their assistance.. hopefully someone might be able to reproduce this, and or resolve it the same way.

Cheers,


----- Original Message -----
From: "Spyro Polymiadis" <spyro@rsp.com.au>
To: "Spyro Polymiadis" <spyro@rsp.com.au>
Cc: "Itamar Heim" <iheim@redhat.com>, "Andrew Dunlop" <ajdunlop@gmail.com>, users@ovirt.org, "Keith Robertson" <kroberts@redhat.com>
Sent: Saturday, 11 February, 2012 5:18:03 PM
Subject: Re: [Users] Unable to add ISOs to default ISO storage domain

ok - here we go.. shed some light on the situation...
it looks like the ISO mount is being mounted as user/group nobody on the hypervisor....

drwxr-xr-x. 3 nobody nobody 4096 Feb 10 02:52 ovirtmgr.foo.com:_mnt_ISO

This might explain it because the vdsm user cannot read the iso as its mode 640 nobody.nobody...

However on the iso domain host - the permissions are correct.. so the hypervisor isnt mounting the path correctly
Its just on the hypervisor node that its mounting as nobody.nobody... i can mount the iso share to any other linux or mac host, and it mounts with id/guid 36.36 as normal...

I initially thought that the user nobody and group nobody were somehow mapped to id 36, but this isnt the case (its normal, 99)...

----- Original Message -----
From: "Spyro Polymiadis" <spyro@rsp.com.au>
To: "Keith Robertson" <kroberts@redhat.com>
Cc: "Itamar Heim" <iheim@redhat.com>, "Andrew Dunlop" <ajdunlop@gmail.com>, users@ovirt.org, "Spyro Polymiadis" <spyro@rsp.com.au>
Sent: Saturday, 11 February, 2012 3:59:20 PM
Subject: Re: [Users] Unable to add ISOs to default ISO storage domain

$ mount ovirtmgr.rsp.com.au:/mnt/ISO test/
$ su - vdsm
This account is currently not available.

In /etc/passwd, the account does not have a valid shell... should it have?

vdsm:x:36:36:Node Virtualization Manager:/var/lib/vdsm:/sbin/nologin


----- Original Message -----
From: "Keith Robertson" <kroberts@redhat.com>
To: "Spyro Polymiadis" <spyro@rsp.com.au>
Cc: "Itamar Heim" <iheim@redhat.com>, "Andrew Dunlop" <ajdunlop@gmail.com>, users@ovirt.org
Sent: Friday, 10 February, 2012 11:59:36 PM
Subject: Re: [Users] Unable to add ISOs to default ISO storage domain

Spyro,

I am also running out of ideas, but I want to verify a few more things
before I can safely say that there isn't a problem with the NFS ISO domain.

On the hyper-visor, can you..
1. mount ovirtmgr.foo.com:/mnt/iso /mnt/isodir
2. su - vdsm
3. cd
/mnt/isodir/23340f35-95ca-4b46-90ec-0c8b83a82786/11111111-1111-1111-1111-111111111111
4. ls

Does that work?

Cheers,
Keith


On 02/09/2012 09:59 PM, Spyro Polymiadis wrote:
> FYI - i also created a new ISO domain, attached it, uploaded my iso - and it still doesnt appear in the webUI
> I also disabled the firewall on both hypervisor and managment servers - but did not make any difference..
>
> does the iso need to be of a specific type? is there some requirement that it must be bootable, or contain an OS, or something else for it not to register?
>
> I still get the message of unknown pool id, pool not connected when i run   vdsClient -s 0 getIsoList fe82b63a-3207-4ce7-a952-ae76a3ef5f24 (with the new pool id)
>
> on the hypervisor, its mounted correctly and i can see the data in /rhev/data-center/mnt/ovirtmgr.foo.com:_mnt_ISO
>
> not sure where to go from here now :(
>
>
> ----- Original Message -----
> From: "Spyro Polymiadis"<spyro@rsp.com.au>
> To: "Keith Robertson"<kroberts@redhat.com>
> Cc: "Itamar Heim"<iheim@redhat.com>, "Andrew Dunlop"<ajdunlop@gmail.com>, users@ovirt.org, "Spyro Polymiadis"<spyro@rsp.com.au>
> Sent: Friday, 10 February, 2012 9:25:20 AM
> Subject: Re: [Users] Unable to add ISOs to default ISO storage domain
>
> yeppers its a test domain..
> the iso path mounts just fine on the hypervisor
> ;)
>
> ----- Original Message -----
> From: "Keith Robertson"<kroberts@redhat.com>
> To: "Spyro Polymiadis"<spyro@rsp.com.au>
> Cc: "Itamar Heim"<iheim@redhat.com>, "Andrew Dunlop"<ajdunlop@gmail.com>, users@ovirt.org
> Sent: Friday, 10 February, 2012 1:31:52 AM
> Subject: Re: [Users] Unable to add ISOs to default ISO storage domain
>
> Looking at the output, I'm a little curious about the address of the NFS
> server for the ISO domain.  You've got this...
> <address>ovirtmgr.foo.com</address>
>
> Can you actually mount that NFS export from your hyper-visor?
>
> Try this...
> 1. On the hyper-visor do this:
> mkdir /mnt/isodir
> 2. mount ovirtmgr.foo.com:/mnt/iso /mnt/isodir
>
> Does that actually work?
>
> Cheers,
> Keith
>
> On 02/09/2012 09:11 AM, Spyro Polymiadis wrote:
>> Heres the output mate - cheers :)
>>
>> DEBUG: URL is https://ovirtmgr.foo.com:8443/api/datacenters
>> DEBUG: Returned XML is
>> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
>> <data_centers>
>>       <data_center href="/api/datacenters/bf61bdea-5265-11e1-bd4b-7b05db53545c" id="bf61bdea-5265-11e1-bd4b-7b05db53545c">
>>           <name>Default</name>
>>           <description>The default Data Center</description>
>>           <link href="/api/datacenters/bf61bdea-5265-11e1-bd4b-7b05db53545c/storagedomains" rel="storagedomains"/>
>>           <link href="/api/datacenters/bf61bdea-5265-11e1-bd4b-7b05db53545c/permissions" rel="permissions"/>
>>           <storage_type>nfs</storage_type>
>>           <storage_format>v1</storage_format>
>>           <version major="3" minor="0"/>
>>           <supported_versions>
>>               <version major="3" minor="0"/>
>>           </supported_versions>
>>           <status>
>>               <state>up</state>
>>           </status>
>>       </data_center>
>> </data_centers>
>>
>> DEBUG: URL is https://ovirtmgr.foo.com:8443/api/datacenters/bf61bdea-5265-11e1-bd4b-7b05db53545c/storagedomains
>> DEBUG: Returned XML is
>> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
>> <storage_domains>
>>       <storage_domain href="/api/datacenters/bf61bdea-5265-11e1-bd4b-7b05db53545c/storagedomains/23340f35-95ca-4b46-90ec-0c8b83a82786" id="23340f35-95ca-4b46-90ec-0c8b83a82786">
>>           <name>ISO</name>
>>           <actions>
>>               <link href="/api/datacenters/bf61bdea-5265-11e1-bd4b-7b05db53545c/storagedomains/23340f35-95ca-4b46-90ec-0c8b83a82786/activate" rel="activate"/>
>>               <link href="/api/datacenters/bf61bdea-5265-11e1-bd4b-7b05db53545c/storagedomains/23340f35-95ca-4b46-90ec-0c8b83a82786/deactivate" rel="deactivate"/>
>>           </actions>
>>           <data_center href="/api/datacenters/bf61bdea-5265-11e1-bd4b-7b05db53545c" id="bf61bdea-5265-11e1-bd4b-7b05db53545c"/>
>>           <type>iso</type>
>>           <status>
>>               <state>active</state>
>>           </status>
>>           <master>false</master>
>>           <storage>
>>               <type>nfs</type>
>>               <address>ovirtmgr.foo.com</address>
>>               <path>/mnt/iso</path>
>>           </storage>
>>           <available>1073741824</available>
>>           <used>3221225472</used>
>>           <committed>0</committed>
>>           <storage_format>v1</storage_format>
>>       </storage_domain>
>>       <storage_domain href="/api/datacenters/bf61bdea-5265-11e1-bd4b-7b05db53545c/storagedomains/a864b2ed-ecb9-4f7b-be7f-c39e214b868f" id="a864b2ed-ecb9-4f7b-be7f-c39e214b868f">
>>           <name>DATASTORE</name>
>>           <actions>
>>               <link href="/api/datacenters/bf61bdea-5265-11e1-bd4b-7b05db53545c/storagedomains/a864b2ed-ecb9-4f7b-be7f-c39e214b868f/activate" rel="activate"/>
>>               <link href="/api/datacenters/bf61bdea-5265-11e1-bd4b-7b05db53545c/storagedomains/a864b2ed-ecb9-4f7b-be7f-c39e214b868f/deactivate" rel="deactivate"/>
>>           </actions>
>>           <data_center href="/api/datacenters/bf61bdea-5265-11e1-bd4b-7b05db53545c" id="bf61bdea-5265-11e1-bd4b-7b05db53545c"/>
>>           <type>data</type>
>>           <status>
>>               <state>active</state>
>>           </status>
>>           <master>true</master>
>>           <storage>
>>               <type>nfs</type>
>>               <address>10.250.1.1</address>
>>               <path>/VMSTORE/RHEV</path>
>>           </storage>
>>           <available>5636070834176</available>
>>           <used>53743999516672</used>
>>           <committed>10737418240</committed>
>>           <storage_format>v1</storage_format>
>>       </storage_domain>
>> </storage_domains>
>>
>> ISO Storage Domain Name   | Datacenter                | ISO Domain Status
>> ISO                       | Default                   | active
>>
>>
>> ----- Original Message -----
>> From: "Keith Robertson"<kroberts@redhat.com>
>> To: "Spyro Polymiadis"<spyro@rsp.com.au>
>> Cc: "Itamar Heim"<iheim@redhat.com>, "Andrew Dunlop"<ajdunlop@gmail.com>, users@ovirt.org
>> Sent: Thursday, 9 February, 2012 9:16:19 PM
>> Subject: Re: [Users] Unable to add ISOs to default ISO storage domain
>>
>> To get us some more information please run...
>>
>> rhevm-iso-uploader list -v
>>
>> On 02/09/2012 03:04 AM, Itamar Heim wrote:
>>> On 02/09/2012 09:59 AM, Spyro Polymiadis wrote:
>>>> i have a data domain (NFS Data master) configured for cluster... yes
>>> and it is active as well at DC level (DC, storage domains)?
>>>
>>>> ----- Original Message -----
>>>> From: "Itamar Heim"<iheim@redhat.com>
>>>> To: "Spyro Polymiadis"<spyro@rsp.com.au>
>>>> Cc: "Andrew Dunlop"<ajdunlop@gmail.com>, users@ovirt.org
>>>> Sent: Thursday, 9 February, 2012 6:22:02 PM
>>>> Subject: Re: [Users] Unable to add ISOs to default ISO storage domain
>>>>
>>>> On 02/09/2012 09:39 AM, Spyro Polymiadis wrote:
>>>>> Thanks for the info..
>>>>>
>>>>> the ISO share is attached to the default domain, and is active, and
>>>>> the host (only 1 hypervisor at the moment) is als part of the same
>>>>> domain.
>>>>> The host is up, and it displays SPM on the right hand side
>>>>>
>>>>> the output of vdsClient is interesting...
>>>>>
>>>>> vdsClient -s 0 getIsoList 23340f35-95ca-4b46-90ec-0c8b83a82786
>>>>> Unknown pool id, pool not connected:
>>>>> ('23340f35-95ca-4b46-90ec-0c8b83a82786',)
>>>> did you create a data domain in this data center?
>>>>
>>>>> ----- Original Message -----
>>>>> From: "Itamar Heim"<iheim@redhat.com>
>>>>> To: "Spyro Polymiadis"<spyro@rsp.com.au>
>>>>> Cc: "Andrew Dunlop"<ajdunlop@gmail.com>, users@ovirt.org
>>>>> Sent: Thursday, 9 February, 2012 5:22:08 PM
>>>>> Subject: Re: [Users] Unable to add ISOs to default ISO storage domain
>>>>>
>>>>> On 02/09/2012 06:18 AM, Spyro Polymiadis wrote:
>>>>>> should actually mention - the issue is that i cannot see/select to
>>>>>> use it in the webUI - even after logging out and back into it
>>>>> 1. is the iso domain attached (and activated) to a DC with an active
>>>>> host in it?
>>>>> 2. check the host is up, and is an SPM (right most column in host grid.
>>>>> 3. run the following command on the host
>>>>> vdsClient -s 0 getIsoList 23340f35-95ca-4b46-90ec-0c8b83a82786
>>>>>
>>>>>> ----- Original Message -----
>>>>>> From: "Spyro Polymiadis"<spyro@rsp.com.au>
>>>>>> To: "Keith Robertson"<kroberts@redhat.com>
>>>>>> Cc: "Andrew Dunlop"<ajdunlop@gmail.com>, users@ovirt.org
>>>>>> Sent: Thursday, 9 February, 2012 2:47:09 PM
>>>>>> Subject: Re: [Users] Unable to add ISOs to default ISO storage domain
>>>>>>
>>>>>> sorry to jump on the bandwagon here - ive also uploaded an iso to
>>>>>> the ISO domain - which i said yes to create it locally on the
>>>>>> engine-management host.
>>>>>> default exported as /mnt/iso - i didnt have to manually do anything
>>>>>> to add it to the domain, only activate it.
>>>>>>
>>>>>> cat /etc/exports
>>>>>> /mnt/iso        0.0.0.0/0.0.0.0(rw)     #rhev installer
>>>>>>
>>>>>>
>>>>>> i uploaded my iso like so:
>>>>>>
>>>>>>       /usr/bin/engine-iso-uploader -i ISO -u admin@internal -r
>>>>>> ovirtmgr.foo.com:8443 upload os_2.0-784729f4-19.iso
>>>>>>
>>>>>> It finished successfully, the iso is owned vdsm.kvm and has the
>>>>>> default 640 permissions.
>>>>>> I tried setting them to 755 as mentioned in one of these threads -
>>>>>> but that didnt help..
>>>>>>
>>>>>> $ tree -pug /mnt/iso
>>>>>>
>>>>>> /mnt/iso
>>>>>>          └── [drwxr-xr-x vdsm     kvm     ]
>>>>>> 23340f35-95ca-4b46-90ec-0c8b83a82786
>>>>>>              ├── [drwxr-xr-x vdsm     kvm     ]  dom_md
>>>>>>              │   ├── [-rw-r--r-- vdsm     kvm     ]  ids
>>>>>>              │   ├── [-rw-r--r-- vdsm     kvm     ]  inbox
>>>>>>              │   ├── [-rw-r--r-- vdsm     kvm     ]  leases
>>>>>>              │   ├── [-rw-r--r-- vdsm     kvm     ]  metadata
>>>>>>              │   └── [-rw-r--r-- vdsm     kvm     ]  outbox
>>>>>>              └── [drwxr-xr-x vdsm     kvm     ]  images
>>>>>>                  └── [drwxr-xr-x vdsm     kvm     ]
>>>>>> 11111111-1111-1111-1111-111111111111
>>>>>>                      └── [-rw-r----- vdsm     kvm     ]
>>>>>> os_2.0-784729f4-19.iso
>>>>>>
>>>>>> I havent rebooted the ovirtmgr host yet incase that "fixes" it
>>> _______________________________________________
>>> Users mailing list
>>> Users@ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/users

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:

...

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

On Fri, Feb 03, 2012 at 09:26:32AM +0000, Andrew Dunlop wrote: 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@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@ovirt.org [mailto:users-bounces@ovirt.org] On Behalf Of Andrew Dunlop Sent: Thursday, February 02, 2012 10:59 AM To: users@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@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@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@ovirt.org http://lists.ovirt.org/mailman/listinfo/users

---

Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users

On 02/06/2012 02:07 PM, Adam Litke wrote:

On Fri, Feb 03, 2012 at 11:34:15AM -0500, Keith Robertson wrote:

...

...

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) Thanks for this suggestion Keith. We're planning to try this and I think it will be a reasonable workaround. In the name of improved usability I would like to consider relaxing this restriction in vdsm as danken has suggested. Security of the data on the mountpoint is really the job of the NFS server and its configuration.

You're welcome. VDSMD appears to be using NFS in the proper manner and any "relaxation" of permissions would need to occur on the NFS server not on the client (i.e. VDSMD), IMHO. NFS's security model (or lack thereof) is based on both UID/GID mapping and control statements in /etc/exports. Assuming the server isn't "squashing", the NFS client must have a UID/GID that allows it to r/w the exported files and directories in accordance with the normal *nix permission set. I'm not sure how you expect to relax this on the VDSMD side unless you're going to have it seteuid/egid to an ID of your choice prior to r/w. Cheers, Keith

--snip--

...

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.

I have a vague, unsubstantiated memory, that this was intentional decision. Maybe it was intended to differentiate RHEV-available images from unrelated files on the same nfs export.

However, I consider this behavior ugly, ununixish, and counter-productive. I wouldn't nack a Vdsm patch that checks readability only, preferably with a backward-compat mode.

Wasn't that set since the ISO domain is a Storage Domain with meta-data? And you do want the rw meta-data to have a specific owner right? You can set global read permission for the images directory however you still won't get rid of the need for having ownership on files, meaning the NFS storage should be able to set ownership. I think you can only really get rid of the ownership limitation by removing the storage domain structure around the ISO-Domain and settle for a mount point. Additionally, it still won't solve the case of having data Storage Domain over NFS - you really need ownership there. The a solution for that, in the case the end users do not have permission to set new users on the storage side and have to result to existing users, will be to allow setting the storage owners users (or for vdsm:kvm so masquerade as that user). Simon.

Dan. _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users