[ovirt-users] oVirt - Node install on CentOS

[Simon Barrett]

One thing I do have to tweak is the group on /var/run/sanlock/sanlock.sock. By default, when I reboot the owner/group/perms are this:

srw-rw---- 1 sanlock root 0 Jun 13 09:08 sanlock.sock

vdsm then has problems accessing sanlock.sock and I see errors like this in engine.log:

2014-06-13 06:18:41,436 INFO  [org.ovirt.engine.core.vdsbroker.vdsbroker.CreateStoragePoolVDSCommand] (org.ovirt.thread.pool-6-thread-17) [12b48409] Command org.ovirt.engine.core.vdsbroker.vdsbroke
r.CreateStoragePoolVDSCommand return value
StatusOnlyReturnForXmlRpc [mStatus=StatusForXmlRpc [mCode=661, mMessage=Cannot acquire host id: ('634aad80-503a-4e59-9738-15b6fb1bf10a', SanlockException(13, 'Sanlock lockspace add failure', 'Permission denied'))]]

If I chgrp qemu /var/run/sanlock/sanlock.sock then all works fine.

I know I can change the default group membership for sanlock in /etc/libvirt/qemu-sanlock.conf but was wondering if this is something that the vdsm install should take care of?

Thanks,

Simon

From: users-bounces at ovirt.org [mailto:users-bounces at ovirt.org] On Behalf Of Joop
Sent: 13 June 2014 11:54
Cc: users at ovirt.org
Subject: Re: [ovirt-users] oVirt - Node install on CentOS

Sven Kieske wrote:

+1 from me, this should work without manual tweaking (except for live

snapshots).



Am 09.06.2014 20:32, schrieb Joop:



If you install a minimal Centos-6.5 and add the ovirt repository and

then add the host using the webui of engine then it will install all

needed packages (vdsm/libvirt/kvm) and you're done. You can then replace

the standard qemu with the one that will do live snapshots. Depending on

where you're storage is located you shouldn't have to tinker with

memberships etc.






Looking at this again I would like the webui install process to add the repo too :-)
If engine-setup is up to date it could know the location  of the ovirt-repo.rpm and install it automatically. There is probably a very good reason why it doesn't do this since I can't imagine I'm the first one to think about this.

Joop
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20140613/8939b91a/attachment.html>