Created attachment 932550 [details] log files and screen shot Description of problem: It reports error as follows when first configure hosted-engine in host. And the network lost its ip address. =============================================================================== [ERROR] Failed to execute stage 'Misc configuration': Command '/bin/vdsClient' failed to execute Version-Release number of selected component (if applicable): rhev-hypervisor7-7.0-20140827.0.iso ovirt-node-3.1.0-0.9.20140815gitee21d9b.el7.noarch ovirt-node-plugin-hosted-engine-0.1.0-0.0.x86_64 ovirt-host-deploy-1.3.0-0.0.1.master.el7.noarch ovirt-hosted-engine-setup-1.2.0-0.2.master.el7.noarch ovirt-hosted-engine-ha-1.2.1-0.3.master.el7.noarch How reproducible: 100% Steps to Reproduce: 1. Install rhev-hypervisor7-7.0-20140827.0.iso 2. Enabled network 3. Configure hosted-engine in shell #ovirt-hosted-engine-setup 4. #ifconfig Actual results: 1. After step3, it will report error as follows. ============================================================================== [ERROR] Failed to execute stage 'Misc configuration': Command '/bin/vdsClient' failed to execute 2. After step4, the network lost its ip address. Expected results: 1. It should setup hosted-engine succeed. Additional info:
Actually in RHEV-H 7.0, firstly we encountered the Bug 1134873 - Report error as 'Hosted Engine HA service are already running on this system' when first configure hosted engine. We need to kill ovirt-hosted-engine-ha service manually in rhevh 7.0, then execute #ovirt-hosted-engine-setup, this bug happened.
Failed command is: 2014-08-28 08:35:45 DEBUG otopi.plugins.ovirt_hosted_engine_setup.network.bridge plugin.execute:866 execute-output: ['/bin/vdsClient', '-s', 'localhost', 'addNetwork', 'bridge=rhevm', 'vlan=', 'bond=', 'nics=enp63s0', 'force=False', 'bridged=True', 'ONBOOT=yes', 'bootproto=dhcp', 'blockingdhcp=true'] stderr: Corresponding to the failure (search for: "2014-08-28 08:35:45", vdsm log shows: Thread-18::DEBUG::2014-08-28 08:35:44,727::BindingXMLRPC::1107::vds::(wrapper) client [127.0.0.1]::call addNetwork with ('rhevm', '', '', ['enp63s0'], {'blockingdhcp': 'true', 'bootproto': 'dhcp', 'force': 'False', 'ONBOOT': 'yes', 'bridged': 'True'}) {} Thread-18::ERROR::2014-08-28 08:35:45,830::BindingXMLRPC::1126::vds::(wrapper) unexpected error Traceback (most recent call last): File "/usr/share/vdsm/rpc/BindingXMLRPC.py", line 1110, in wrapper File "/usr/share/vdsm/rpc/BindingXMLRPC.py", line 521, in addNetwork File "/usr/share/vdsm/API.py", line 1363, in addNetwork File "/usr/share/vdsm/supervdsm.py", line 50, in __call__ File "/usr/share/vdsm/supervdsm.py", line 48, in <lambda> File "<string>", line 2, in addNetwork File "/usr/lib64/python2.7/multiprocessing/managers.py", line 773, in _callmethod IOError: [Errno 2] No such file or directory: '/var/run/vdsm/trackedInterfaces/rhevm' Looks like filesystem tree is not complete on rhev-hypervisor7.
It seems that the file init/systemd/vdsm-tmpfiles.d.conf.in is responsible for telling systemd tmpfilesd to create the missing dir. Looking at the ISO I can not find that file in /usr/lib/tmpfiles.d. Also rpm -ql vdsm does not show the tmpfilesd file. Could it be that the file is not packaged in the used vdsm build: vdsm-4.16.0-1.el7
Maybe, move this bug to vdsm component then so they can check why the file is missing there.
Oved, the whole /usr/lib/tmpfiles.d/vdsm.conf was missing from the rpm, not only the network-owned file. So strictly speaking - it's infra bug. I don't know what has gone wrong with vdsm-4.16.0-1.el7.x86_64.rpm, but more recent builds, done by dcaro, seems to be fine: $ rpm -qpl vdsm-4.16.3-1.el7.x86_64.rpm|grep tmp /usr/lib/tmpfiles.d/vdsm.conf
Test version: rhev-hypervisor7-7.0-20140904.0.iso ovirt-node-3.1.0-0.10.20140904gitb828c37.el7.noarch vdsm-4.16.3-2.el7.x86_64 Test step: 1. Install rhev-hypervisor7-7.0-20140904.0.iso 2. Enabled network 3. Configure hosted-engine in shell #ovirt-hosted-engine-setup 4. #rpm -ql vdsm-4.16.3-2.el7.x86_64 | grep vdsm.conf Test result: 1. After step3, it can continue without error. 2. After step4, the output is as follows. #rpm -ql vdsm-4.16.3-2.el7.x86_64 | grep vdsm.conf /etc/modules-load.d/vdsm.conf /etc/security/limits.d/99-vdsm.conf /etc/sysctl.d/vdsm.conf /etc/vdsm/vdsm.conf /usr/lib/tmpfiles.d/vdsm.conf /usr/share/doc/vdsm-4.16.3/vdsm.conf.sample So this issue is fixed in vdsm-4.16.3-2.el7.x86_64.
Verified in rhev-hypervisor7-7.0-20141006.0 vdsm-4.16.6-1.el7.x86_64