[ovirt-users] Modules sanlock are not configured

[Jurriën Bloemen]

Hi all,

I have CentOS 7 running and I added the oVirt 3.5 repo to it. I open the oVirt Manager and added a new system to it. 
The manager says installing and after that is fails to connect. Looking on the system I see:

Mar 30 21:09:37 vdsmd_init_common.sh[7106]: vdsm: Running mkdirs
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: vdsm: Running configure_coredump
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: vdsm: Running configure_vdsm_logs
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: vdsm: Running wait_for_network
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: vdsm: Running run_init_hooks
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: vdsm: Running upgraded_version_check
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: vdsm: Running check_is_configured
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: Error:
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: One of the modules is not configured to work with VDSM.
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: To configure the module use the following:
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: 'vdsm-tool configure [--module module-name]'.
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: If all modules are not configured try to use:
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: 'vdsm-tool configure --force'
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: (The force flag will stop the module's service and start it
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: afterwards automatically to load the new configuration.)
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: libvirt is already configured for vdsm
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: Modules sanlock are not configured
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: vdsm: stopped during execute check_is_configured task (task returned with error code 1).

So I run vdsm-tool configure after I stop sanlock. 

# vdsm-tool configure

Checking configuration status...

libvirt is already configured for vdsm
SUCCESS: ssl configured to true. No conflicts

Running configure...
Reconfiguration of sanlock is done.

Done configuring modules to VDSM.

But when I want to start vdsmd it still gives the error that sanlock is not configured.

Does somebody has a solution for this? 

I am a bit lost on this… Google only tells me that there was a bug in 3.4. 

Thanks in advance,

Jurriën
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20150330/ef388bd5/attachment.html>