Version-Release number of selected component: vdsm-python-4.14.8.1-0.fc20 Additional info: reporter: libreport-2.2.2 cmdline: /usr/bin/python /usr/bin/vdsm-tool is-configured executable: /usr/bin/vdsm-tool kernel: 3.14.6-200.fc20.x86_64 runlevel: unknown type: Python uid: 0 Truncated backtrace: configurator.py:273:isconfigured:RuntimeError: One of the modules is not configured to work with VDSM. To configure the module use the following: 'vdsm-tool configure [module_name]'. If all modules are not configured try to use: 'vdsm-tool configure --force' (The force flag will stop the module's service and start it afterwards automatically to load the new 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.7/site-packages/vdsm/tool/configurator.py", line 273, in isconfigured raise RuntimeError(msg) RuntimeError: One of the modules is not configured to work with VDSM. To configure the module use the following: 'vdsm-tool configure [module_name]'. If all modules are not configured try to use: 'vdsm-tool configure --force' (The force flag will stop the module's service and start it afterwards automatically to load the new configuration.) Local variables in innermost frame: msg: "\n\nOne of the modules is not configured to work with VDSM.\nTo configure the module use the following:\n'vdsm-tool configure [module_name]'.\n\nIf all modules are not configured try to use:\n'vdsm-tool configure --force'\n(The force flag will stop the module's service and start it\nafterwards automatically to load the new configuration.)\n" c: <vdsm.tool.configurator.SanlockModuleConfigure object at 0x7f8ae8fbf610> args: Namespace(modules=['libvirt', 'sanlock']) m: ['libvirt'] ret: False Potential duplicate: bug 1097356
Created attachment 914352 [details] File: backtrace
Created attachment 914353 [details] File: dead.letter
Created attachment 914354 [details] File: environ
*** Bug 1097356 has been marked as a duplicate of this bug. ***
Vdsm might ran here manually without configure its related modules. This bug doesn't provide specific scenario that leads this state, therefore closing the bug on INSUFFICIENT_DATA