Re: [ovirt-users] FC20 vdsmd broken after latest yum update

Hi, after a maintenance of one of our hosts, vdsmd does not start anymore. Error could be narrowed down to the following command: [root ~]# /usr/bin/vdsm-tool is-configured 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 251, in isconfigured if c.getName() in args.modules and not c.isconfigured() File "/usr/lib64/python2.7/site-packages/vdsm/tool/configurator.py", line 103, in isconfigured self._exec_libvirt_configure("check_if_configured") File "/usr/lib64/python2.7/site-packages/vdsm/tool/configurator.py", line 78, in _exec_libvirt_configure raw=True, File "/usr/lib64/python2.7/site-packages/vdsm/utils.py", line 645, in execCmd deathSignal=deathSignal, childUmask=childUmask) File "/usr/lib64/python2.7/site-packages/cpopen/__init__.py", line 50, in __init__ stderr=PIPE) File "/usr/lib64/python2.7/subprocess.py", line 711, in __init__ errread, errwrite) TypeError: _execute_child_v275() takes exactly 17 arguments (18 given) We are on Ovirt 3.4.2. FC20 Hypervisor node is fully patched (as mentioned above). Any idea what is going wrong?