Re: [Users] Uploaded ISO file doesn't show up in admin portal
disabling nfsv4 in /etc/sysconfig/nfs (adding -N 4 to the start up options) was a work around for me to make my uploaded iso appear. see my previous thread on this list ----- Original Message ----- From: "Maor" <mlipchuk@redhat.com> To: "Terry Phelps" <tgphelps50@gmail.com> Cc: users@ovirt.org Sent: Saturday, 25 February, 2012 5:57:07 AM Subject: Re: [Users] Uploaded ISO file doesn't show up in admin portal On 02/24/2012 10:23 PM, Douglas Landgraf wrote:
Hi Terry,
On 02/24/2012 02:51 PM, Douglas Landgraf wrote:
On 02/24/2012 10:28 AM, Terry Phelps wrote:
It looks like you were doing this as root, so I did, too. In any case, the result looks good to me:
# mount | grep iso
oravm3.acbl.net:/isodomain/ on /rhev/data-center/mnt/oravm3.acbl.net:_isodomain type nfs4 (rw,relatime,vers=4,rsize=524288,wsize=524288,namlen=255,soft,nosharecache,proto=tcp,port=0,timeo=600,retrans=6,sec=sys,clientaddr=172.16.2.52,minorversion=0,local_lock=none,addr=192.168.118.10)
]# ls /rhev/data-center/mnt/oravm3.acbl.net:_isodomain
48a5390f-2f86-485c-8537-b6bc9dd71796 vdsmTest
[root@oravm2 ~]# vdsClient -s 0 getFileList 48a5390f-2f86-485c-8537-b6bc9dd71796
file: OracleLinux-R6-U2-Server-x86_64-dvd.iso status: {'status': 469, 'ctime': '1330092866.03', 'size': '3591360512'}
NOTE: That "vdsmTest" file you see has appeared there since yesterday, I think. I didn't put it there.
You didn't, this file can be removed, yesterday the nfs-check couldn't complete the test (remove the file) as you answered me (below) and it's still there.
# python nfs-check.py oravm3.acbl.net:/isodomain Current hostname: oravm2.acbl.net - IP addr 127.0.0.1 Trying to /bin/mount -t nfs oravm3.acbl.net:/isodomain... Executing NFS tests.. Removing vdsmTest file.. Traceback (most recent call last): File "nfs-check.py", line 268, in<module> os.removedirs(LOCALPATH) File "/usr/lib64/python2.7/os.py", line 170, in removedirs OSError: [Errno 16] Device or resource busy: '/tmp/tmpV9KEh5'
Just to confirm, during the execution of nfs-check have you manually entry into /tmp/tmpV9KEh5 (from another shell)? If not, this EBUSY error might be like symptom of this weird behaviour...
However, let me continue... looking the previous messages of this thread, looks like you have the iso correctly uploaded. Have you tried to restart jboss-as service (oVirt Engine) to see if your iso appears into the GUI?
BTW, most of ovirt people are available to chat and help 'on-the-fly' at irc.oftc.net, channel #ovirt , fell free to join us there .
Hi Terry, The engine.log should contain logs regarding ISO files, can you please attach it to the mail, maybe we can find some clues there. Regards, Maor _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Hi Spyro, thanks for the advice, I didn't tried this approach before, but its definitely worth trying if it solved your problem. I was thinking first, trying some little troubleshooting, Terry, I saw in one response, part of this thread, you were added a file named "me", by touching it in the ISO mounted directory. Can you please try the following: mv me me.iso sudo chown 36:36 me.iso #(36:36 equals to vdsm:kvm) and then try to run getIsoList as before: vdsClient -s 0 getIsoList 9775f154-7578-4e22-ae44-4664b298a8cc If it still didn't return any files, try changing the file mode (just a hunch on this) sudo chmod 666 me.iso Hope it works, if it does, we can try to troubleshooting the other files. On 02/25/2012 02:34 AM, Spyro Polymiadis wrote:
disabling nfsv4 in /etc/sysconfig/nfs (adding -N 4 to the start up options) was a work around for me to make my uploaded iso appear.
see my previous thread on this list
----- Original Message ----- From: "Maor" <mlipchuk@redhat.com> To: "Terry Phelps" <tgphelps50@gmail.com> Cc: users@ovirt.org Sent: Saturday, 25 February, 2012 5:57:07 AM Subject: Re: [Users] Uploaded ISO file doesn't show up in admin portal
On 02/24/2012 10:23 PM, Douglas Landgraf wrote:
Hi Terry,
On 02/24/2012 02:51 PM, Douglas Landgraf wrote:
On 02/24/2012 10:28 AM, Terry Phelps wrote:
It looks like you were doing this as root, so I did, too. In any case, the result looks good to me:
# mount | grep iso
oravm3.acbl.net:/isodomain/ on /rhev/data-center/mnt/oravm3.acbl.net:_isodomain type nfs4 (rw,relatime,vers=4,rsize=524288,wsize=524288,namlen=255,soft,nosharecache,proto=tcp,port=0,timeo=600,retrans=6,sec=sys,clientaddr=172.16.2.52,minorversion=0,local_lock=none,addr=192.168.118.10)
]# ls /rhev/data-center/mnt/oravm3.acbl.net:_isodomain
48a5390f-2f86-485c-8537-b6bc9dd71796 vdsmTest
[root@oravm2 ~]# vdsClient -s 0 getFileList 48a5390f-2f86-485c-8537-b6bc9dd71796
file: OracleLinux-R6-U2-Server-x86_64-dvd.iso status: {'status': 469, 'ctime': '1330092866.03', 'size': '3591360512'}
NOTE: That "vdsmTest" file you see has appeared there since yesterday, I think. I didn't put it there.
You didn't, this file can be removed, yesterday the nfs-check couldn't complete the test (remove the file) as you answered me (below) and it's still there.
# python nfs-check.py oravm3.acbl.net:/isodomain Current hostname: oravm2.acbl.net - IP addr 127.0.0.1 Trying to /bin/mount -t nfs oravm3.acbl.net:/isodomain... Executing NFS tests.. Removing vdsmTest file.. Traceback (most recent call last): File "nfs-check.py", line 268, in<module> os.removedirs(LOCALPATH) File "/usr/lib64/python2.7/os.py", line 170, in removedirs OSError: [Errno 16] Device or resource busy: '/tmp/tmpV9KEh5'
Just to confirm, during the execution of nfs-check have you manually entry into /tmp/tmpV9KEh5 (from another shell)? If not, this EBUSY error might be like symptom of this weird behaviour...
However, let me continue... looking the previous messages of this thread, looks like you have the iso correctly uploaded. Have you tried to restart jboss-as service (oVirt Engine) to see if your iso appears into the GUI?
BTW, most of ovirt people are available to chat and help 'on-the-fly' at irc.oftc.net, channel #ovirt , fell free to join us there .
Hi Terry, The engine.log should contain logs regarding ISO files, can you please attach it to the mail, maybe we can find some clues there.
Regards, Maor _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
On Sat, Feb 25, 2012 at 5:13 AM, Maor <mlipchuk@redhat.com> wrote:
Hi Spyro, thanks for the advice, I didn't tried this approach before, but its definitely worth trying if it solved your problem.
I was thinking first, trying some little troubleshooting, Terry, I saw in one response, part of this thread, you were added a file named "me", by touching it in the ISO mounted directory. Can you please try the following: mv me me.iso sudo chown 36:36 me.iso #(36:36 equals to vdsm:kvm) and then try to run getIsoList as before: vdsClient -s 0 getIsoList 9775f154-7578-4e22-ae44-4664b298a8cc
If it still didn't return any files, try changing the file mode (just a hunch on this) sudo chmod 666 me.iso
Hope it works, if it does, we can try to troubleshooting the other files.
From the ovirt-engine, I did "touch me.iso" to create a new iso file, and did a chown to 36:36. The me.iso, and NOT the real one, showed up in the admin portal. From the node, as root, I did the "ls -l" which showed me.iso with
Hey, this DID work: vdsClient -s 0 getConnectedStoragePoolsList f465251e-5679-11e1-ba81-97917332892e [root@oravm2 11111111-1111-1111-1111-111111111111]# vdsClient -s 0 getIsoList f465251e-5679-11e1-ba81-97917332892e ------ ISO list with proper permissions only ------- me.iso An "ls -l" shows: # ls -l total 3507192 -rw-r--r--. 1 4294967294 4294967294 0 Feb 25 16:26 me.iso -rw-r-----. 1 4294967294 4294967294 3591360512 Feb 24 14:14 OracleLinux-R6-U2-Server-x86_64-dvd.iso 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. 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: bash-4.2$ ls -l total 3507192 -rw-r--r--. 1 4294967294 4294967294 0 Feb 25 16:26 me.iso -rw-r--r--. 1 4294967294 4294967294 3591360512 Feb 24 14:14 OracleLinux-R6-U2-Server-x86_64-dvd.iso bash-4.2$ history|grep vdsC 34 history|grep vdsC bash-4.2$ vdsClient -s 0 getIsoList f465251e-5679-11e1-ba81-97917332892e ------ ISO list with proper permissions only ------- me.iso OracleLinux-R6-U2-Server-x86_64-dvd.iso 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. Now, I'm really confused, so let me summarize what I did: permissions as 644, but the real ISO showed 640.
From the node, I tried, as root, to change the real ISO permissions to 644. It wouldn't let me. 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. I looked back at admin portal, after doing all this, and refereshed the ISODomain images panel. BOTH files showed up.
As best I can tell, the only thing I did was to manually create the me.iso file and do the chown.
On 02/25/2012 06:57 PM, Terry Phelps wrote:
On Sat, Feb 25, 2012 at 5:13 AM, Maor <mlipchuk@redhat.com <mailto:mlipchuk@redhat.com>> wrote:
Hi Spyro, thanks for the advice, I didn't tried this approach before, but its definitely worth trying if it solved your problem.
I was thinking first, trying some little troubleshooting, Terry, I saw in one response, part of this thread, you were added a file named "me", by touching it in the ISO mounted directory. Can you please try the following: mv me me.iso sudo chown 36:36 me.iso #(36:36 equals to vdsm:kvm) and then try to run getIsoList as before: vdsClient -s 0 getIsoList 9775f154-7578-4e22-ae44-4664b298a8cc
If it still didn't return any files, try changing the file mode (just a hunch on this) sudo chmod 666 me.iso
Hope it works, if it does, we can try to troubleshooting the other files.
Hey, this DID work:
vdsClient -s 0 getConnectedStoragePoolsList f465251e-5679-11e1-ba81-97917332892e
[root@oravm2 11111111-1111-1111-1111-111111111111]# vdsClient -s 0 getIsoList f465251e-5679-11e1-ba81-97917332892e ------ ISO list with proper permissions only ------- me.iso
An "ls -l" shows:
# ls -l total 3507192 -rw-r--r--. 1 4294967294 4294967294 0 Feb 25 16:26 me.iso -rw-r-----. 1 4294967294 4294967294 3591360512 Feb 24 14:14 OracleLinux-R6-U2-Server-x86_64-dvd.iso
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.
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:
bash-4.2$ ls -l total 3507192 -rw-r--r--. 1 4294967294 4294967294 0 Feb 25 16:26 me.iso -rw-r--r--. 1 4294967294 4294967294 3591360512 Feb 24 14:14 OracleLinux-R6-U2-Server-x86_64-dvd.iso bash-4.2$ history|grep vdsC 34 history|grep vdsC bash-4.2$ vdsClient -s 0 getIsoList f465251e-5679-11e1-ba81-97917332892e ------ ISO list with proper permissions only ------- me.iso OracleLinux-R6-U2-Server-x86_64-dvd.iso
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.
Now, I'm really confused, so let me summarize what I did:
From the ovirt-engine, I did "touch me.iso" to create a new iso file, and did a chown to 36:36. The me.iso, and NOT the real one, showed up in the admin portal. From the node, as root, I did the "ls -l" which showed me.iso with permissions as 644, but the real ISO showed 640. From the node, I tried, as root, to change the real ISO permissions to 644. It wouldn't let me. 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. I looked back at admin portal, after doing all this, and refereshed the ISODomain images panel. BOTH files showed up.
As best I can tell, the only thing I did was to manually create the me.iso file and do the chown.
well, i assume this isn't relevant since it took you enough time, but adding the iso to the domain manually won't make it appear in the UI for a few minutes until the refresh happens, less you click the refresh button manually in the UI (I could be wrong - details around the implementation of how/when iso list is refreshed have been changed recently)
participants (4)
-
Itamar Heim -
Maor -
Spyro Polymiadis -
Terry Phelps