Version-Release number of selected component: vdsm-python-4.14.8.1-1.fc21 Additional info: reporter: libreport-2.3.0 cmdline: /usr/bin/python /usr/bin/vdsm-tool is-configured executable: /usr/bin/vdsm-tool kernel: 3.18.8-201.fc21.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 0x7f748e83e7d0> args: Namespace(modules=['libvirt', 'sanlock']) m: ['libvirt'] ret: False Potential duplicate: bug 1097356
Created attachment 1004192 [details] File: backtrace
Created attachment 1004193 [details] File: environ
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.