On 2/23/12, Keith Robertson <kroberts@redhat.com> wrote:
On 02/23/2012 02:21 PM, Terry Phelps wrote:
Thanks for the quick reply.
My one hypervisor already had the ISO domain mounted (without any explicit action by me): This is to be expected. VDSM needs the mount. I suggested that command just in case it wasn't mounted for some odd reason. 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)
Using this mount (I didn't do exactly what you said, if that matters), Nope, you're fine. I did the tests you asked for. Yes, I can touch a new file. Yes, I can read the ISO file
Here is what I saw:
I'm assuming you were "vdsm" when you executed these commands, right?
bash-4.2$ ls OracleLinux-R6-U2-Server-x86_64-dvd.iso bash-4.2$ touch me bash-4.2$ ls me OracleLinux-R6-U2-Server-x86_64-dvd.iso bash-4.2$ strings Orac* |head -2 CD001 LINUX OL6.2 x86_64 Disc 1 20111212
Funny, though. When I typed "su - vdsm" by mistake, from root, it said "This account is currently not available." (Is that relevant?) But what you said to do did work fine. By default vdsm is given a nologin shell for security reasons. The "-s /bin/bash" overrides that when switching users. Other ideas/ Not at the moment. I think you've done a fairly good job of demonstrating that VDSM would not have any permission problems reading or writing to the NFS export.
Just to gather more information, I re-ran engine-iso-uploader to upload my ISO. It complained that the ISO was already there, which it IS. I used the "--force" option to make him do it again. He did. It still doesn't show up in the admin portal. Is there something else I can do to help find the problem?