<div dir="ltr">Hi,<div><br></div><div>I am testing oVirt 4.2, I am using nested KVM for that.</div><div>I am using two hypervisors Centos 7 updated and the hosted-Engine deployment using the ovirt appliance.</div><div>For storage I am using iscsi and NFS4</div><div><br></div><div>Versions I am using :</div><div><span style="font-family:monospace"><span style="font-weight:bold;color:rgb(255,84,84)">ovirt</span><span style="color:rgb(0,0,0)">-engine-appliance-4.2-20180214.1.el7.centos.noarch</span><br></span></div><div><span style="font-family:monospace"><span style="font-weight:bold;color:rgb(255,84,84)">ovirt</span><span style="color:rgb(0,0,0)">-hosted-engine-setup-2.2.9-1.el7.centos.noarch</span><br></span></div><div><span style="font-family:monospace"><span style="font-weight:bold;color:rgb(255,84,84)">kernel</span><span style="color:rgb(0,0,0)">-3.10.0-693.21.1.el7.x86_64</span><br></span></div><div><br></div><div>I have a problem deploying the hosted-engine VM, when configuring the deployment (hosted-engine --deploy), it asks for the engine's hostname then the engine's IP address, I use static IP, in my lab I used <b>192.168.1.104</b> as IP for the VM engine, and I choose to add the it's hostname entry to the hypervisors's /etc/hosts</div><div><br></div><div>But the deployment get stuck every time in the same place : <span style="color:rgb(0,0,0);font-family:monospace"><b>TASK [Wait for the host to become non operational]</b></span></div><div><br></div><div>After some time, it gave up and the deployment fails.</div><div><br></div><div>I don't know the reason for now, but I have seen this behavior in <b>/etc/hosts </b>of the hypervisor.</div><div><br></div><div>In the beginning of the deployment the entry <span style="color:rgb(0,0,0);font-family:monospace"><b>192.168.2.104 engine01.example.local</b> is added, then sometime after that it's deleted, then a new entry is added with this IP </span><span style="font-family:monospace"><b style=""><span style="background-color:rgb(255,255,255)"><font color="#ff0000">192.168.122.65</font></span><font color="#000000"> engine01.wodel.wd</font></b><font color="#000000"> which has nothing to do with the network I am using.</font></span></div><div><span style="color:rgb(0,0,0);font-family:monospace"><br></span></div><div><span style="color:rgb(0,0,0);font-family:monospace">Here is the error I am seeing in the deployment log</span></div><div><span style="color:rgb(0,0,0);font-family:monospace"><br></span></div><div><span style="font-family:monospace"><span style="color:rgb(0,0,0)">2018-03-24 11:51:31,398+0100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:100 TASK [Wait </span><br>for the host to become non operational]
<br>2018-03-24 12:02:07,284+0100 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:94 {u'_ansible<br>_parsed': True, u'_ansible_no_log': False, u'changed': False, u'attempts': 150, u'invocation': {u'module_args': {u'pattern': <br>u'name=hyperv01.wodel.wd', u'fetch_nested': False, u'nested_attributes': []}}, u'ansible_facts': {u'ovirt_hosts': []}}
<br>2018-03-24 12:02:07,385+0100 ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:98 fatal: [loc<br>alhost]: FAILED! => {"ansible_facts": {"ovirt_hosts": []}, "attempts": 150, "changed": false}
<br>2018-03-24 12:02:07,587+0100 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:94 PLAY RECAP <br>[engine01.wodel.wd] : ok: 15 changed: 8 unreachable: 0 skipped: 4 failed: 0
<br>2018-03-24 12:02:07,688+0100 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:94 PLAY RECAP <br>[localhost] : ok: 41 changed: 14 unreachable: 0 skipped: 3 failed: 1
<br>2018-03-24 12:02:07,789+0100 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils.run:180 ansible-playbook rc: 2
<br>2018-03-24 12:02:07,790+0100 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils.run:187 ansible-playbook stdou<br>t:<br></span></div><div><span style="font-family:monospace"><span style="color:rgb(0,0,0)">2018-03-24 12:02:07,791+0100 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils.run:189 to retry, use: --limi</span><br>t @/usr/share/ovirt-hosted-engine-setup/ansible/bootstrap_local_vm.retry
<br>
<br>2018-03-24 12:02:07,791+0100 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils.run:190 ansible-playbook stder<br>r:
<br>2018-03-24 12:02:07,792+0100 DEBUG otopi.context context._executeMethod:143 method exception
<br>Traceback (most recent call last):
<br> File "/usr/lib/python2.7/site-packages/otopi/context.py", line 133, in _executeMethod
<br> method['method']()
<br> File "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/gr-he-ansiblesetup/core/misc.py", line 186, in _closeup
<br> r = ah.run()
<br> File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_setup/ansible_utils.py", line 194, in run
<br> raise RuntimeError(_('Failed executing ansible-playbook'))
<br>RuntimeError: Failed executing ansible-playbook
<br>2018-03-24 12:02:07,795+0100 ERROR otopi.context context._executeMethod:152 Failed to execute stage 'Closing up': Failed exec<br>uting ansible-playbook<br>
<br></span></div><div><span style="color:rgb(0,0,0);font-family:monospace"><br></span></div><div><span style="color:rgb(0,0,0);font-family:monospace">any idea????</span></div><div><br></div><div><br></div><div>Regards</div></div>