Attachment 895186 Details for Bug 1097356 – File: backtrace

File: backtrace

backtrace (text/plain), 1.56 KB, created by Bob Doolittle on 2014-05-13 15:50:54 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Bob Doolittle

Created: 2014-05-13 15:50:54 UTC

Size: 1.56 KB

patch

obsolete

>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 0x7f8cec338610>
>args: Namespace(modules=['libvirt', 'sanlock'])
>m: ['libvirt']
>ret: False

Actions: View

Attachments on bug 1097356: 895186 | 895187