Bug 1097356

Summary: [abrt] vdsm-python: configurator.py:273:isconfigured:RuntimeError:
Product: [Fedora] Fedora Reporter: Bob Doolittle <bzrh.bobd>
Component: vdsmAssignee: Yaniv Bronhaim <ybronhei>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: danken, dougsland, fsimonce, virt-maint, ybronhei
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/475edc824fabddd5806dc4e9a0a96b74d6a6038a
Whiteboard: abrt_hash:eea8f8495a9252053bbed0f4653c918214d0c467
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-09-29 11:36:45 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: environ none

Description Bob Doolittle 2014-05-13 15:50:49 UTC 
Description of problem:
yum install ovirt-hosted-engine-setup on a freshly installed F19 system.
I did downgrade sos and added "exclude=sos" to yum.conf as per release notes for 3.4.1

Version-Release number of selected component:
vdsm-python-4.14.8.1-0.fc19

Additional info:
reporter:       libreport-2.2.1
cmdline:        /usr/bin/python /usr/bin/vdsm-tool is-configured
executable:     /usr/bin/vdsm-tool
kernel:         3.13.11-100.fc19.x86_64
runlevel:       N 5
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 0x7f8cec338610>
args: Namespace(modules=['libvirt', 'sanlock'])
m: ['libvirt']
ret: False
Comment 1 Bob Doolittle 2014-05-13 15:50:54 UTC 
Created attachment 895186 [details]
File: backtrace
Comment 2 Bob Doolittle 2014-05-13 15:50:57 UTC 
Created attachment 895187 [details]
File: environ
Comment 3 Yaniv Bronhaim 2014-09-29 11:36:45 UTC 

*** This bug has been marked as a duplicate of bug 1115784 ***