Description of problem: Traceback (most recent call last): File "/bin/vdsm-tool", line 145, in <module> sys.exit(main()) File "/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 244, in configure File "/usr/lib64/python2.7/site-packages/vdsm/tool/configurator.py", line 96, in configure File "/usr/lib64/python2.7/site-packages/vdsm/tool/configurator.py", line 93, in _exec_libvirt_configure RuntimeError: Failed to perform libvirt action. Version-Release number of selected component (if applicable): vdsm-4.14.13-2.el7ev.x86_64 vdsm-reg-4.14.13-2.el7ev.noarch ovirt-node-plugin-vdsm-0.1.2-3.el7ev.noarch libvirt-1.1.1-29.el7_0.1.x86_64 How reproducible: Steps to Reproduce: 1. Auto install RHEV-H 7.0 2. 3. Actual results: Expected results: Additional info:
Is this maybe the same problem as in bug 1144279?
I don't understand the issue here at all. Please provide specific steps for the auto installation so we'll understand how you do it and try it here is it 100% reproducible? After the rhel installation is done, does it start the deploy phase (the approve)? If yes, can you attach also the host-deploy log? other than that, can you attach the syslog\journalctl output about libvirt\vdsm ? can you run "vdsm-tool configure --force" manually and see the output? does it fail there?
is this a 3.5 issue? vdsm 3.5 uses 4.16.3 we removed _exec_libvirt_configure at 4.16.0 p.s AFAIK vdsm-reg & ovirt-node-plugin-vdsm are only on node, no?
thanks for the steps, but you have it already reproduced .. please save us from installing rhevh for now and add the logs - host-deploy, vdsm, libvirt, syslog and engine's . did you try to run - vdsm-tool configure --force and checked the output? did it fail? can we ssh to that host and check that ? it should be related to the rhev-h installation and the recent changes that we did around the configuration , as it doesn't happen on other distributions. we just need to investigate what is missing on reproduced environment and watch the logs
(In reply to Yaniv Bronhaim from comment #6) > thanks for the steps, but you have it already reproduced .. please save us > from installing rhevh for now and add the logs - host-deploy, vdsm, libvirt, > syslog and engine's . Hey Yaniv, I'll try to get you the logs. The problem here is that the issues comes up during a non-interactive auto-installation, where I do not have access to the logs. > did you try to run - vdsm-tool configure --force and checked the output? did > it fail? can we ssh to that host and check that ? > > it should be related to the rhev-h installation and the recent changes that > we did around the configuration , as it doesn't happen on other > distributions. we just need to investigate what is missing on reproduced > environment and watch the logs As said above, that is a bit difficult as it is a non-interactive automatic installation. I try to get them ASAP.
Some updates. I just tested 3.5 on 7.0 and could not reproduce the problem there. The tested version was using vdsm-4.16.5-2.el7 ovirt-node-3.1.0-0.17.20140925git29c3403.el7 I'll now download the 3.4.z build to see if I can reproduce it there.
Thanks. As per comment 4 the above exception names a function removed at 3.5 as part of bug 1084770. Waiting for the 3.4.z results.
Note is not relevant to 3.5 but to 3.4.4 only
No rhev-h 7.0 available, cannot reproduce on el7.0.