<br><br><div class="gmail_quote">On Sat, Feb 25, 2012 at 5:13 AM, Maor <span dir="ltr"><<a href="mailto:mlipchuk@redhat.com">mlipchuk@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Spyro, thanks for the advice,<br>
I didn't tried this approach before, but its definitely worth trying if<br>
it solved your problem.<br>
<br>
I was thinking first, trying some little troubleshooting,<br>
Terry, I saw in one response, part of this thread, you were added a file<br>
named "me", by touching it in the ISO mounted directory.<br>
Can you please try the following:<br>
mv me me.iso<br>
sudo chown 36:36 me.iso #(36:36 equals to vdsm:kvm)<br>
and then try to run getIsoList as before:<br>
vdsClient -s 0 getIsoList 9775f154-7578-4e22-ae44-4664b298a8cc<br>
<br>
If it still didn't return any files, try changing the file mode (just a<br>
hunch on this)<br>
sudo chmod 666 me.iso<br>
<br>
Hope it works, if it does, we can try to troubleshooting the other files.<br><br></blockquote></div><br>Hey, this DID work:<br><br>vdsClient -s 0 getConnectedStoragePoolsList<br>f465251e-5679-11e1-ba81-97917332892e<br><br>
[root@oravm2 11111111-1111-1111-1111-111111111111]# vdsClient -s 0 getIsoList f465251e-5679-11e1-ba81-97917332892e<br>------ ISO list with proper permissions only -------<br>me.iso<br><br>An "ls -l" shows:<br><br>
# ls -l<br>total 3507192<br>-rw-r--r--. 1 4294967294 4294967294 0 Feb 25 16:26 me.iso<br>-rw-r-----. 1 4294967294 4294967294 3591360512 Feb 24 14:14 OracleLinux-R6-U2-Server-x86_64-dvd.iso<br><br>The only difference I can see is the 644 and 640 permissions. Let me change the real .iso to 644 and see what happens. I changed the permissions to be both 644 on the ovirt engine, but when I look at the node, the permissions on the real ISO file is still 640. And vdsClient doesn't show it.<br>
<br>Oh, wait! I ran the above vdsClient and "ls -l" as root on the node. root could not change the permissions on the ISO, so I switched to run as vdsm. When I look at things when running as vdsm, both the permissions and vdsClient look the same for both files:<br>
<br><br>bash-4.2$ ls -l<br>total 3507192<br>-rw-r--r--. 1 4294967294 4294967294 0 Feb 25 16:26 me.iso<br>-rw-r--r--. 1 4294967294 4294967294 3591360512 Feb 24 14:14 OracleLinux-R6-U2-Server-x86_64-dvd.iso<br>bash-4.2$ history|grep vdsC<br>
34 history|grep vdsC<br>bash-4.2$ vdsClient -s 0 getIsoList f465251e-5679-11e1-ba81-97917332892e<br>------ ISO list with proper permissions only -------<br>me.iso<br>OracleLinux-R6-U2-Server-x86_64-dvd.iso<br><br>Oh! I just looked back at the admin portal, and it sees both ISO files now. But I haven't touched the real one that I never could see all along. <br>
<br>Now, I'm really confused, so let me summarize what I did:<br><br>From the ovirt-engine, I did "touch me.iso" to create a new iso file, and did a chown to 36:36.<br>The me.iso, and NOT the real one, showed up in the admin portal.<br>
>From the node, as root, I did the "ls -l" which showed me.iso with permissions as 644, but the real ISO showed 640.<br>From the node, I tried, as root, to change the real ISO permissions to 644. It wouldn't let me.<br>
>From the node, I switched to run as vdsm, to try to change the permissions. But, as vdsm, "ls -l" showed both files as 644.<br>I looked back at admin portal, after doing all this, and refereshed the ISODomain images panel. BOTH files showed up.<br>
<br>As best I can tell, the only thing I did was to manually create the me.iso file and do the chown.<br><br><br><br><br><br><br>