Why "vdsm-tool configure --force" does not configure qemu.conf properly in the first run on a fresh install in RHS 3.0 ?
Issue
-
Why "vdsm-tool configure --force" does not configure qemu.conf properly in the first run on a fresh install in RHS 3.0 ?
-
snippet from console logs:
initctl: Job is already running: libvirtd
vdsm: Running mkdirs
vdsm: Running configure_coredump
vdsm: Running configure_vdsm_logs
vdsm: Running run_init_hooks
vdsm: Running gencerts
vdsm: Running check_is_configured
libvirt is already configured for vdsm
sanlock service is already configured
vdsm: Running validate_configuration
FAILED: conflicting vdsm and libvirt-qemu tls configuration.
vdsm.conf with ssl=True requires the following changed:
libvirtd.conf: listen_tcp=0, auth_tcp="sasl",
qemu.conf: spice_tls=1.
Modules libvirt contains invalid configuration
Traceback (most recent call last):
File "/usr/bin/vdsm-tool", line 145, in <module>
sys.exit(main())
File "/usr/bin/vdsm-tool", line 142, in main
return tool_command[cmd]["command"](*args[1:])
File "/usr/lib64/python2.6/site-packages/vdsm/tool/configurator.py", line 296, in validate_config
raise RuntimeError("Config is not valid. Check conf files")
RuntimeError: Config is not valid. Check conf files
vdsm: stopped during execute validate_configuration task (task returned with error code 1).
vdsm start [FAILED]
Environment
- Red Hat Gluster Storage 3.0
- vdsm 4.14.7.3-1.el6rhs.x86_64
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.