<p dir="ltr"><br>
Il giorno 19/set/2013 19:10, "Alexander Wels" <<a href="mailto:awels@redhat.com">awels@redhat.com</a>> ha scritto:<br>
><br>
> Steve,<br>
><br>
> <br>
><br>
> Having just installed gluster on my local hosts and seeing the exact same error in my setup. I am going to assume the following are true:<br>
><br>
> <br>
><br>
> 1. You made a partition just for gluster.<br>
><br>
> 2. You followed oVirt 3.3, Glusterized article from Jason Brooks.<br>
><br>
> <br>
><br>
> I got the exact same error because for some reason the owner of the directory I put the gluster bricks in keep changing back to root instead of kvm:kvm. Each time I reboot my host, that happens, so I am assuming I didn't set up something correctly. But you can solve it by chowning the directory and everything will work again.<br>
><br>
> <br>
><br>
> If that doesn't help, well I don't know, I just started using it myself, I just happen to have seen the same error at some point.<br>
><br>
> <br>
><br>
> Alexander<br>
><br>
> <br>
><br>
> On Thursday, September 19, 2013 12:26:52 PM Steve Dainard wrote:<br>
><br>
> Hello,<br>
><br>
><br>
> New Ovirt 3.3 install on Fedora 19.<br>
><br>
><br>
> When I try to add a gluster storage domain I get the following:<br>
><br>
><br>
> UI error:<br>
><br>
> Error while executing action Add Storage Connection: Permission settings on the specified path do not allow access to the storage.<br>
><br>
> Verify permission settings on the specified storage path.<br>
><br>
><br>
> VDSM logs contain:<br>
><br>
> Thread-393::DEBUG::2013-09-19 11:59:42,399::BindingXMLRPC::177::vds::(wrapper) client [10.0.0.34]<br>
><br>
> Thread-393::DEBUG::2013-09-19 11:59:42,399::task::579::TaskManager.Task::(_updateState) Task=`12c38fec-0072-4974-a8e3-9125b3908246`::moving from state init -> state preparing<br>
><br>
> Thread-393::INFO::2013-09-19 11:59:42,400::logUtils::44::dispatcher::(wrapper) Run and protect: connectStorageServer(domType=7, spUUID='00000000-0000-0000-0000-000000000000', conList=[{'port': '', 'connection': '192.168.1.1:/rep2-virt', 'iqn': '', 'portal': '', 'user': '', 'vfs_type': 'glusterfs', 'password': '******', 'id': '00000000-0000-0000-0000-000000000000'}], options=None)<br>
><br>
> Thread-393::DEBUG::2013-09-19 11:59:42,405::mount::226::Storage.Misc.excCmd::(_runcmd) '/usr/bin/sudo -n /usr/bin/mount -t glusterfs 192.168.1.1:/rep2-virt /rhev/data-center/mnt/glusterSD/192.168.1.1:_rep2-virt' (cwd None)<br>
><br>
> Thread-393::DEBUG::2013-09-19 11:59:42,490::mount::226::Storage.Misc.excCmd::(_runcmd) '/usr/bin/sudo -n /usr/bin/umount -f -l /rhev/data-center/mnt/glusterSD/192.168.1.1:_rep2-virt' (cwd None)<br>
><br>
> Thread-393::ERROR::2013-09-19 11:59:42,505::hsm::2382::Storage.HSM::(connectStorageServer) Could not connect to storageServer<br>
><br>
> Traceback (most recent call last):<br>
><br>
> File "/usr/share/vdsm/storage/hsm.py", line 2379, in connectStorageServer<br>
><br>
> conObj.connect()<br>
><br>
> File "/usr/share/vdsm/storage/storageServer.py", line 227, in connect<br>
><br>
> raise e<br>
><br>
> StorageServerAccessPermissionError: Permission settings on the specified path do not allow access to the storage. Verify permission settings on the specified storage path.: 'path = /rhev/data-center/mnt/glusterSD/192.168.1.1:_rep2-virt'<br>
><br>
> Thread-393::DEBUG::2013-09-19 11:59:42,506::hsm::2396::Storage.HSM::(connectStorageServer) knownSDs: {}<br>
><br>
> Thread-393::INFO::2013-09-19 11:59:42,506::logUtils::47::dispatcher::(wrapper) Run and protect: connectStorageServer, Return response: {'statuslist': [{'status': 469, 'id': '00000000-0000-0000-0000-000000000000'}]}<br>
><br>
> Thread-393::DEBUG::2013-09-19 11:59:42,506::task::1168::TaskManager.Task::(prepare) Task=`12c38fec-0072-4974-a8e3-9125b3908246`::finished: {'statuslist': [{'status': 469, 'id': '00000000-0000-0000-0000-000000000000'}]}<br>
><br>
> Thread-393::DEBUG::2013-09-19 11:59:42,506::task::579::TaskManager.Task::(_updateState) Task=`12c38fec-0072-4974-a8e3-9125b3908246`::moving from state preparing -> state finished<br>
><br>
> Thread-393::DEBUG::2013-09-19 11:59:42,506::resourceManager::939::ResourceManager.Owner::(releaseAll) Owner.releaseAll requests {} resources {}<br>
><br>
> Thread-393::DEBUG::2013-09-19 11:59:42,507::resourceManager::976::ResourceManager.Owner::(cancelAll) Owner.cancelAll requests {}<br>
><br>
> Thread-393::DEBUG::2013-09-19 11:59:42,507::task::974::TaskManager.Task::(_decref) Task=`12c38fec-0072-4974-a8e3-9125b3908246`::ref 0 aborting False<br>
><br>
><br>
> Other info:<br>
><br>
> - I have two nodes, ovirt001, ovirt002 they are both Fedora 19.<br>
><br>
> - The gluster bricks are replicated and located on the nodes. (ovirt001:rep2-virt, ovirt002:rep2-virt)<br>
><br>
> - Local directory for the mount, I changed permissions on glusterSD to 777, it was 755, and there is nothing in that directory:<br>
><br>
> [root@ovirt001 mnt]# pwd<br>
><br>
> /rhev/data-center/mnt<br>
><br>
> [root@ovirt001 mnt]# ll<br>
><br>
> total 4<br>
><br>
> drwxrwxrwx. 2 vdsm kvm 4096 Sep 19 12:18 glusterSD<br>
><br>
><br>
> I find it odd that the UUID's listed in the vdsm logs are zero's..<br>
><br>
><br>
> Appreciate any help,<br>
><br>
><br>
><br>
> Steve<br>
><br>
><br>
><br>
><br>
> _______________________________________________<br>
> Users mailing list<br>
> <a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>
> <a href="http://lists.ovirt.org/mailman/listinfo/users">http://lists.ovirt.org/mailman/listinfo/users</a><br>
><br>
I had a similar problem in gluster configuration for openstack and found solution in this ovirt page:</p>
<p dir="ltr"><a href="http://www.ovirt.org/Features/GlusterFS_Storage_Domain#Setting_up_a_GlusterFS_storage_volume_for_using_it_as_a_storage_domain">http://www.ovirt.org/Features/GlusterFS_Storage_Domain#Setting_up_a_GlusterFS_storage_volume_for_using_it_as_a_storage_domain</a></p>
<p dir="ltr">In particular:</p>
<p dir="ltr">If the GlusterFS volume was created manually, then ensure the below options are set on the volume, so that its accessible from oVirtvolume set <volname> storage.owner-uid=36volume set <volname> storage.owner-gid=36</p>
<p dir="ltr">Check that otherwise each time a node mounts the gluster it will reset permissions root. ..<br>
Hih<br>
Gianluca</p>