On 24 Mar 2018, at 12:13, wodel youchi <wodel.youchi@gmail.com> wrote: =20 Hi, =20 I am testing oVirt 4.2, I am using nested KVM for that. I am using two hypervisors Centos 7 updated and the hosted-Engine deployme= nt using the ovirt appliance. For storage I am using iscsi and NFS4 =20 Versions I am using : ovirt-engine-appliance-4.2-20180214.1.el7.centos.noarch ovirt-hosted-engine-setup-2.2.9-1.el7.centos.noarch kernel-3.10.0-693.21.1.el7.x86_64 =20 I have a problem deploying the hosted-engine VM, when configuring the depl= oyment (hosted-engine --deploy), it asks for the engine's hostname then the e= ngine's IP address, I use static IP, in my lab I used 192.168.1.104 as IP fo= r the VM engine, and I choose to add the it's hostname entry to the hypervis= ors's /etc/hosts =20 But the deployment get stuck every time in the same place : TASK [Wait for=
--Apple-Mail-97559372-1475-4E35-824D-C6C124121D92 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hello, I also have done a installation on my host running KVM and I =E2=80=98m pret= ty sure my vm=E2=80=99s can only use the 192.168.122.0/24 range if you insta= ll them with NAT networking when creating them. So that might explain why yo= u see that address appear in your log and also explain why the engine system= can=E2=80=99t be reached. Kind regards. the host to become non operational]
=20 After some time, it gave up and the deployment fails. =20 I don't know the reason for now, but I have seen this behavior in /etc/hos= ts of the hypervisor. =20 In the beginning of the deployment the entry 192.168.2.104 engine01.examp= le.local is added, then sometime after that it's deleted, then a new entry i= s added with this IP 192.168.122.65 engine01.wodel.wd which has nothing to d= o with the network I am using. =20 Here is the error I am seeing in the deployment log =20 2018-03-24 11:51:31,398+0100 INFO otopi.ovirt_hosted_engine_setup.ansible_= utils ansible_utils._process_output:100 TASK [Wait=20 for the host to become non operational]=20 2018-03-24 12:02:07,284+0100 DEBUG otopi.ovirt_hosted_engine_setup.ansible= _utils ansible_utils._process_output:94 {u'_ansible _parsed': True, u'_ansible_no_log': False, u'changed': False, u'attempts':= 150, u'invocation': {u'module_args': {u'pattern':=20 u'name=3Dhyperv01.wodel.wd', u'fetch_nested': False, u'nested_attributes':= []}}, u'ansible_facts': {u'ovirt_hosts': []}}=20 2018-03-24 12:02:07,385+0100 ERROR otopi.ovirt_hosted_engine_setup.ansible= _utils ansible_utils._process_output:98 fatal: [loc alhost]: FAILED! =3D> {"ansible_facts": {"ovirt_hosts": []}, "attempts": 1= 50, "changed": false}=20 2018-03-24 12:02:07,587+0100 DEBUG otopi.ovirt_hosted_engine_setup.ansible= _utils ansible_utils._process_output:94 PLAY RECAP=20 [engine01.wodel.wd] : ok: 15 changed: 8 unreachable: 0 skipped: 4 failed: 0= =20 2018-03-24 12:02:07,688+0100 DEBUG otopi.ovirt_hosted_engine_setup.ansible= _utils ansible_utils._process_output:94 PLAY RECAP=20 [localhost] : ok: 41 changed: 14 unreachable: 0 skipped: 3 failed: 1=20 2018-03-24 12:02:07,789+0100 DEBUG otopi.ovirt_hosted_engine_setup.ansible= _utils ansible_utils.run:180 ansible-playbook rc: 2=20 2018-03-24 12:02:07,790+0100 DEBUG otopi.ovirt_hosted_engine_setup.ansible= _utils ansible_utils.run:187 ansible-playbook stdou t: 2018-03-24 12:02:07,791+0100 DEBUG otopi.ovirt_hosted_engine_setup.ansible= _utils ansible_utils.run:189 to retry, use: --limi t @/usr/share/ovirt-hosted-engine-setup/ansible/bootstrap_local_vm.retry=20=
=20 2018-03-24 12:02:07,791+0100 DEBUG otopi.ovirt_hosted_engine_setup.ansible= _utils ansible_utils.run:190 ansible-playbook stder r:=20 2018-03-24 12:02:07,792+0100 DEBUG otopi.context context._executeMethod:14= 3 method exception=20 Traceback (most recent call last):=20 File "/usr/lib/python2.7/site-packages/otopi/context.py", line 133, in _e= xecuteMethod=20 method['method']()=20 File "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/gr-he-ansib= lesetup/core/misc.py", line 186, in _closeup=20 r =3D ah.run()=20 File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_setup/ansible_= utils.py", line 194, in run=20 raise RuntimeError(_('Failed executing ansible-playbook'))=20 RuntimeError: Failed executing ansible-playbook=20 2018-03-24 12:02:07,795+0100 ERROR otopi.context context._executeMethod:15= 2 Failed to execute stage 'Closing up': Failed exec uting ansible-playbook =20 =20 any idea???? =20 =20 Regards _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Versions I am using :</div><div><span style=3D"font-family:monospace"><span=
<div><br></div><div>After some time, it gave up and the deployment fails.</=
<font color=3D"#000000"> which has nothing to do with the network I am= using.</font></span></div><div><span style=3D"color:rgb(0,0,0);font-family:= monospace"><br></span></div><div><span style=3D"color:rgb(0,0,0);font-family= :monospace">Here is the error I am seeing in the deployment log</span></div>= <div><span style=3D"color:rgb(0,0,0);font-family:monospace"><br></span></div= <div><span style=3D"font-family:monospace"><span style=3D"color:rgb(0,0,0)"= 2018-03-24 11:51:31,398+0100 INFO otopi.ovirt_hosted_engine_setup.ansible_u= tils 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.ansib= le_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=3Dhyperv01.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.ansib= le_utils ansible_utils._process_output:98 fatal: [loc<br>alhost]: FAILED! =3D= > {"ansible_facts": {"ovirt_hosts": []}, "attempts": 150, "changed": fals= e} <br>2018-03-24 12:02:07,587+0100 DEBUG otopi.ovirt_hosted_engine_setup.ansib= le_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.ansib= le_utils ansible_utils._process_output:94 PLAY RECAP <br>[localhost] : ok: 4= 1 changed: 14 unreachable: 0 skipped: 3 failed: 1 <br>2018-03-24 12:02:07,789+0100 DEBUG otopi.ovirt_hosted_engine_setup.ansib= le_utils ansible_utils.run:180 ansible-playbook rc: 2 <br>2018-03-24 12:02:07,790+0100 DEBUG otopi.ovirt_hosted_engine_setup.ansib= le_utils ansible_utils.run:187 ansible-playbook stdou<br>t:<br></span></div>= <div><span style=3D"font-family:monospace"><span style=3D"color:rgb(0,0,0)">= 2018-03-24 12:02:07,791+0100 DEBUG otopi.ovirt_hosted_engine_setup.ansible_u= tils ansible_utils.run:189 to retry, use: --limi</span><br>t @/usr/sha= re/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.ansib= le_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 13= 3, 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 =3D 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-playbo= ok')) <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-playb= ook<br> <br></span></div><div><span style=3D"color:rgb(0,0,0);font-family:monospace"= <br></span></div><div><span style=3D"color:rgb(0,0,0);font-family:monospace= ">any idea????</span></div><div><br></div><div><br></div><div>Regards</div><= /div> </div></blockquote><blockquote type=3D"cite"><div><span>____________________= ___________________________</span><br><span>Users mailing list</span><br><sp= an><a href=3D"mailto:Users@ovirt.org">Users@ovirt.org</a></span><br><span><a=
--Apple-Mail-97559372-1475-4E35-824D-C6C124121D92 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable <html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D= utf-8"></head><body dir=3D"auto"><div></div><div>Hello,</div><div><br></div>= <div>I also have done a installation on my host running KVM and I =E2=80=98m= pretty sure my vm=E2=80=99s can only use the 192.168.122.0/24 range if you i= nstall them with NAT networking when creating them. So that might explain wh= y you see that address appear in your log and also explain why the engine sy= stem can=E2=80=99t be reached.</div><div><br></div><div>Kind regards.</div><= div><br>On 24 Mar 2018, at 12:13, wodel youchi <<a href=3D"mailto:wodel.y= ouchi@gmail.com">wodel.youchi@gmail.com</a>> wrote:<br><br></div><blockqu= ote type=3D"cite"><div><div dir=3D"ltr">Hi,<div><br></div><div>I am testing o= Virt 4.2, I am using nested KVM for that.</div><div>I am using two hyperviso= rs Centos 7 updated and the hosted-Engine deployment using the ovirt applian= ce.</div><div>For storage I am using iscsi and NFS4</div><div><br></div><div= style=3D"font-weight:bold;color:rgb(255,84,84)">ovirt</span><span style=3D"= color:rgb(0,0,0)">-engine-appliance-4.2-20180214.1.el7.centos.noarch</span><= br></span></div><div><span style=3D"font-family:monospace"><span style=3D"fo= nt-weight:bold;color:rgb(255,84,84)">ovirt</span><span style=3D"color:rgb(0,= 0,0)">-hosted-engine-setup-2.2.9-1.el7.centos.noarch</span><br></span></div>= <div><span style=3D"font-family:monospace"><span style=3D"font-weight:bold;c= olor:rgb(255,84,84)">kernel</span><span style=3D"color:rgb(0,0,0)">-3.10.0-6= 93.21.1.el7.x86_64</span><br></span></div><div><br></div><div>I have a probl= em deploying the hosted-engine VM, when configuring the deployment (hosted-e= ngine --deploy), it asks for the engine's hostname then the engine's IP addr= ess, I use static IP, in my lab I used <b>192.168.1.104</b> as IP for t= he 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 ti= me in the same place : <span style=3D"color:rgb(0,0,0);font-family:mono= space"><b>TASK [Wait for the host to become non operational]</b></span></div= div><div><br></div><div>I don't know the reason for now, but I have seen thi= s behavior in <b>/etc/hosts </b>of the hypervisor.</div><div><br></div><div>= In the beginning of the deployment the entry <span style=3D"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 wit= h this IP </span><span style=3D"font-family:monospace"><b style=3D""><s= pan style=3D"background-color:rgb(255,255,255)"><font color=3D"#ff0000">192.= 168.122.65</font></span><font color=3D"#000000"> engine01.wodel.wd</font></b= href=3D"http://lists.ovirt.org/mailman/listinfo/users">http://lists.ovirt.o= rg/mailman/listinfo/users</a></span><br></div></blockquote></body></html>= --Apple-Mail-97559372-1475-4E35-824D-C6C124121D92--