
Hi, 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 deployment using the ovirt appliance. For storage I am using iscsi and NFS4 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 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 *192.168.1.104* as IP for the VM engine, and I choose to add the it's hostname entry to the hypervisors's /etc/hosts But the deployment get stuck every time in the same place : *TASK [Wait for the host to become non operational]* After some time, it gave up and the deployment fails. I don't know the reason for now, but I have seen this behavior in */etc/hosts *of the hypervisor. In the beginning of the deployment the entry *192.168.2.104 engine01.example.local* is added, then sometime after that it's deleted, then a new entry is added with this IP *192.168.122.65 engine01.wodel.wd* which has nothing to do with the network I am using. Here is the error I am seeing in the deployment log 2018-03-24 11:51:31,398+0100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:100 TASK [Wait for the host to become non operational] 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': u'name=hyperv01.wodel.wd', u'fetch_nested': False, u'nested_attributes': []}}, u'ansible_facts': {u'ovirt_hosts': []}} 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! => {"ansible_facts": {"ovirt_hosts": []}, "attempts": 150, "changed": false} 2018-03-24 12:02:07,587+0100 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:94 PLAY RECAP [engine01.wodel.wd] : ok: 15 changed: 8 unreachable: 0 skipped: 4 failed: 0 2018-03-24 12:02:07,688+0100 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:94 PLAY RECAP [localhost] : ok: 41 changed: 14 unreachable: 0 skipped: 3 failed: 1 2018-03-24 12:02:07,789+0100 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils.run:180 ansible-playbook rc: 2 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 2018-03-24 12:02:07,791+0100 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils.run:190 ansible-playbook stder r: 2018-03-24 12:02:07,792+0100 DEBUG otopi.context context._executeMethod:143 method exception Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/otopi/context.py", line 133, in _executeMethod method['method']() File "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/gr-he-ansiblesetup/core/misc.py", line 186, in _closeup r = ah.run() File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_setup/ansible_utils.py", line 194, in run raise RuntimeError(_('Failed executing ansible-playbook')) RuntimeError: Failed executing ansible-playbook 2018-03-24 12:02:07,795+0100 ERROR otopi.context context._executeMethod:152 Failed to execute stage 'Closing up': Failed exec uting ansible-playbook any idea???? Regards

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--

Hello,
I also have done a installation on my host running KVM and I =E2=80=98m=
This is a multi-part message in MIME format. --------------DEBF3B25067683F7CA71AF9F Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 03/24/2018 01:40 PM, Andy Michielsen wrote: pretty
sure my vm=E2=80=99s can only use the 192.168.122.0/24 range if you ins= tall them with NAT networking when creating them. So that might explain why you see that address appear in your log and also explain why the engine system can=E2=80=99t be reached.
Can't tell fo sure about other installations, yet IMHO problem is with networking schema. One need to set bridge to real ethernet interface and add it to KVM VM definition. For example, my SuSE box have 2 ethernet cards, 192.168.0.aa for SMB fle server and another bridged with IP 192.168.0.bb defined within KVM guest (CentOS 7.4 with oVirt host engine). See configs below. Another SuSE box have 10 Ethernet interfaces, one for for its own needs, and 4 + 3 for VyOS routers running as KVM guests. ****************************** SU47:/etc/sysconfig/network # tail -n 100 ifcfg-br0 BOOTPROTO=3D'static' BRIDGE=3D'yes' BRIDGE_FORWARDDELAY=3D'0' BRIDGE_PORTS=3D'eth0' BRIDGE_STP=3D'off' BROADCAST=3D'' DHCLIENT_SET_DEFAULT_ROUTE=3D'no' ETHTOOL_OPTIONS=3D'' IPADDR=3D'' MTU=3D'' NETWORK=3D'' PREFIXLEN=3D'24' REMOTE_IPADDR=3D'' STARTMODE=3D'auto' NAME=3D'' SU47:/etc/sysconfig/network # tail -n 100 ifcfg-eth0 BOOTPROTO=3D'none' BROADCAST=3D'' DHCLIENT_SET_DEFAULT_ROUTE=3D'no' ETHTOOL_OPTIONS=3D'' IPADDR=3D'' MTU=3D'' NAME=3D'82579LM Gigabit Network Connection' NETMASK=3D'' NETWORK=3D'' REMOTE_IPADDR=3D'' STARTMODE=3D'auto' PREFIXLEN=3D''
Kind regards.
On 24 Mar 2018, at 12:13, wodel youchi <wodel.youchi@gmail.com <mailto:wodel.youchi@gmail.com>> wrote:
Hi,
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 deployment using the ovirt appliance. For storage I am using iscsi and NFS4
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
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 *192.168.1.104*=C2=A0as IP for the VM engine, and I choose to add=
the
it's hostname entry to the hypervisors's /etc/hosts
But the deployment get stuck every time in the same place :=C2=A0*TASK [Wait for the host to become non operational]*
After some time, it gave up and the deployment fails.
I don't know the reason for now, but I have seen this behavior in */etc/hosts *of the hypervisor.
In the beginning of the deployment the entry=C2=A0 *192.168.2.104 engine01.example.local* is added, then sometime after that it's deleted, then a new entry is added with this IP=C2=A0*192.168.122.65engine01.wodel.wd*=C2=A0which has nothing to do= with the network I am using.
Here is the error I am seeing in the deployment log
2018-03-24 11:51:31,398+0100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:100 TASK [Wait for the host to become non operational] 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': u'name=3Dhyperv01.wodel.wd', u'fetch_nested': False, u'nested_attributes': []}}, u'ansible_facts': {u'ovirt_hosts': []}} 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": 150, "changed": false} 2018-03-24 12:02:07,587+0100 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:94 PLAY RECAP [engine01.wodel.wd] : ok: 15 changed: 8 unreachable: 0 skipped: 4 failed: 0 2018-03-24 12:02:07,688+0100 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:94 PLAY RECAP [localhost] : ok: 41 changed: 14 unreachable: 0 skipped: 3 failed: 1 2018-03-24 12:02:07,789+0100 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils.run:180 ansible-playbook rc: 2 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 =C2=A0to retry, use: --limi t @/usr/share/ovirt-hosted-engine-setup/ansible/bootstrap_local_vm.ret= ry
2018-03-24 12:02:07,791+0100 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils.run:190 ansible-playbook stder r: 2018-03-24 12:02:07,792+0100 DEBUG otopi.context context._executeMethod:143 method exception Traceback (most recent call last): =C2=A0File "/usr/lib/python2.7/site-packages/otopi/context.py", line 1= 33, in _executeMethod =C2=A0=C2=A0=C2=A0method['method']() =C2=A0File "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/gr-he-ansible= setup/core/misc.py", line 186, in _closeup =C2=A0=C2=A0=C2=A0r =3D ah.run() =C2=A0File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_setup/ansible_ut= ils.py", line 194, in run =C2=A0=C2=A0=C2=A0raise RuntimeError(_('Failed executing ansible-playb= ook')) RuntimeError: Failed executing ansible-playbook 2018-03-24 12:02:07,795+0100 ERROR otopi.context context._executeMethod:152 Failed to execute stage 'Closing up': Failed exec uting ansible-playbook
any idea????
Regards _______________________________________________ Users mailing list Users@ovirt.org <mailto:Users@ovirt.org> http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
--------------DEBF3B25067683F7CA71AF9F 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=3Dutf= -8"> </head> <body bgcolor=3D"#FFFFFF" text=3D"#000000"> <div class=3D"moz-cite-prefix">On 03/24/2018 01:40 PM, Andy Michielse= n wrote:<br> </div> <blockquote type=3D"cite" cite=3D"mid:41136397-BF14-4DCE-9762-C4FA40EFBBA8@gmail.com"> <meta http-equiv=3D"content-type" content=3D"text/html; charset=3Du= tf-8"> <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.1= 22.0/24 range if you install them with NAT networking when creating them. So that might explain why you see that address appear in your log and also explain why the engine system can=E2=80=99t be reached.<= /div> </blockquote> <br> Can't tell fo sure about other installations, yet IMHO problem is with networking schema.<br> <br> One need to set bridge to real ethernet interface and add it to KVM VM definition.<br> <br> For example, my SuSE box have 2 ethernet cards, 192.168.0.aa for SMB fle server and another bridged with IP 192.168.0.bb defined within KVM guest (CentOS 7.4 with oVirt host engine). See configs below.<br> <br> Another SuSE box have 10 Ethernet interfaces, one for for its own needs, and 4 + 3 for VyOS routers running as KVM guests.<br> <br> ******************************<br> <br> SU47:/etc/sysconfig/network # tail -n 100 ifcfg-br0 <br> BOOTPROTO=3D'static'<br> BRIDGE=3D'yes'<br> BRIDGE_FORWARDDELAY=3D'0'<br> BRIDGE_PORTS=3D'eth0'<br> BRIDGE_STP=3D'off'<br> BROADCAST=3D''<br> DHCLIENT_SET_DEFAULT_ROUTE=3D'no'<br> ETHTOOL_OPTIONS=3D''<br> IPADDR=3D''<br> MTU=3D''<br> NETWORK=3D''<br> PREFIXLEN=3D'24'<br> REMOTE_IPADDR=3D''<br> STARTMODE=3D'auto'<br> NAME=3D''<br> <br> SU47:/etc/sysconfig/network # tail -n 100 ifcfg-eth0 <br> BOOTPROTO=3D'none'<br> BROADCAST=3D''<br> DHCLIENT_SET_DEFAULT_ROUTE=3D'no'<br> ETHTOOL_OPTIONS=3D''<br> IPADDR=3D''<br> MTU=3D''<br> NAME=3D'82579LM Gigabit Network Connection'<br> NETMASK=3D''<br> NETWORK=3D''<br> REMOTE_IPADDR=3D''<br> STARTMODE=3D'auto'<br> PREFIXLEN=3D''<br> <br> <br> <blockquote type=3D"cite" cite=3D"mid:41136397-BF14-4DCE-9762-C4FA40EFBBA8@gmail.com"> <div><br> </div> <div>Kind regards.</div> <div><br> On 24 Mar 2018, at 12:13, wodel youchi <<a href=3D"mailto:wodel.youchi@gmail.com" moz-do-not-send=3D"true"=
wodel.youchi@gmail.com</a>> wrote:<br> <br> </div> <blockquote type=3D"cite"> <div> <div dir=3D"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=3D"font-family:monospace"><span style=3D"font-weight:bold;color:rgb(255,84,84)">ovirt</= span><span style=3D"color:rgb(0,0,0)">-engine-appliance-4.2-201802= 14.1.el7.centos.noarch</span><br> </span></div> <div><span style=3D"font-family:monospace"><span style=3D"font-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;color:rgb(255,84,84)">kernel<= /span><span style=3D"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>=C2=A0as 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 :=C2=A0<span style=3D"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.</d= iv> <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=C2=A0 <span style=3D"color:rgb(0,0,0);font-family:monospace"><b>192.1= 68.2.104 engine01.example.local</b> is added, then sometime after that it's deleted, then a new entry is added with this IP=C2=A0</span><span style=3D"font-family:monospace"= <b style=3D""><span 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><font color=3D"#000000">=C2=A0which has nothing to do with th= e 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">H= ere is the error I am seeing in the deployment log</span></di= v> <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_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=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.ansible_utils ansible_utils._process_output:98 fatal: [loc<br> alhost]: FAILED! =3D> {"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=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_utils ansible_utils.run:189 =C2=A0to retry, use: --limi</span=
<br> t @/usr/share/ovirt-hosted-engine-setup/ansible/bootstrap_l= ocal_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> =C2=A0File "/usr/lib/python2.7/site-packages/otopi/context.py", line 133, in _executeMethod <br> =C2=A0=C2=A0=C2=A0method['method']() <br> =C2=A0File "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/gr-he-ansibleset= up/core/misc.py", line 186, in _closeup <br> =C2=A0=C2=A0=C2=A0r =3D ah.run() <br> =C2=A0File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_setup/ansible_utils= .py", line 194, in run <br> =C2=A0=C2=A0=C2=A0raise 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=3D"color:rgb(0,0,0);font-family:monospace"><= br> </span></div> <div><span style=3D"color:rgb(0,0,0);font-family:monospace">a= ny 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> <span><a href=3D"mailto:Users@ovirt.org" moz-do-not-send=3D"tru= e">Users@ovirt.org</a></span><br> <span><a href=3D"http://lists.ovirt.org/mailman/listinfo/users" moz-do-not-send=3D"true">http://lists.ovirt.org/mailman/lis= tinfo/users</a></span><br> </div> </blockquote> <br> <fieldset class=3D"mimeAttachmentHeader"></fieldset> <br> <pre wrap=3D"">_______________________________________________ Users mailing list <a class=3D"moz-txt-link-abbreviated" href=3D"mailto:Users@ovirt.org">Use= rs@ovirt.org</a> <a class=3D"moz-txt-link-freetext" href=3D"http://lists.ovirt.org/mailman= /listinfo/users">http://lists.ovirt.org/mailman/listinfo/users</a> </pre> </blockquote> <p><br> </p> </body> </html>
--------------DEBF3B25067683F7CA71AF9F--

Hi and thanks for your replies, I cleaned up everything and started from scratch. I using nested-kvm for my test with host-passthrough to expose vmx to the VM hypervisor, my physical CPU is a Core i5 6500 This time I had another problem, the VM engine won't start because of this error in vdsm.log 2018-03-27 22:48:31,893+0100 ERROR (vm/c9c0640e) [virt.vm] (vmId='c9c0640e-d8f1-4ade-95f3-40f2982b1d8c') The vm start process failed (vm:927) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 856, in _startUnderlyingVm self._run() File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 2756, in _run dom.createWithFlags(flags) File "/usr/lib/python2.7/site-packages/vdsm/common/libvirtconnection.py", line 130, in wrapper ret = f(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/common/function.py", line 92, in wrapper return func(inst, *args, **kwargs) File "/usr/lib64/python2.7/site-packages/libvirt.py", line 1069, in createWithFlags if ret == -1: raise libvirtError ('virDomainCreateWithFlags() failed', dom=self) libvirtError:* internal error: Unknown CPU model SkylakeClient* The CPU model *SkylakeClient* presented to the VM engine is not recognized. is there a way to bypass this? Regards. 2018-03-24 16:25 GMT+01:00 Andrei Verovski <andreil1@starlett.lv>:
On 03/24/2018 01:40 PM, Andy Michielsen wrote:
Hello,
I also have done a installation on my host running KVM and I ‘m pretty sure my vm’s can only use the 192.168.122.0/24 range if you install them with NAT networking when creating them. So that might explain why you see that address appear in your log and also explain why the engine system can’t be reached.
Can't tell fo sure about other installations, yet IMHO problem is with networking schema.
One need to set bridge to real ethernet interface and add it to KVM VM definition.
For example, my SuSE box have 2 ethernet cards, 192.168.0.aa for SMB fle server and another bridged with IP 192.168.0.bb defined within KVM guest (CentOS 7.4 with oVirt host engine). See configs below.
Another SuSE box have 10 Ethernet interfaces, one for for its own needs, and 4 + 3 for VyOS routers running as KVM guests.
******************************
SU47:/etc/sysconfig/network # tail -n 100 ifcfg-br0 BOOTPROTO='static' BRIDGE='yes' BRIDGE_FORWARDDELAY='0' BRIDGE_PORTS='eth0' BRIDGE_STP='off' BROADCAST='' DHCLIENT_SET_DEFAULT_ROUTE='no' ETHTOOL_OPTIONS='' IPADDR='' MTU='' NETWORK='' PREFIXLEN='24' REMOTE_IPADDR='' STARTMODE='auto' NAME=''
SU47:/etc/sysconfig/network # tail -n 100 ifcfg-eth0 BOOTPROTO='none' BROADCAST='' DHCLIENT_SET_DEFAULT_ROUTE='no' ETHTOOL_OPTIONS='' IPADDR='' MTU='' NAME='82579LM Gigabit Network Connection' NETMASK='' NETWORK='' REMOTE_IPADDR='' STARTMODE='auto' PREFIXLEN=''
Kind regards.
On 24 Mar 2018, at 12:13, wodel youchi <wodel.youchi@gmail.com> wrote:
Hi,
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 deployment using the ovirt appliance. For storage I am using iscsi and NFS4
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
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 *192.168.1.104* as IP for the VM engine, and I choose to add the it's hostname entry to the hypervisors's /etc/hosts
But the deployment get stuck every time in the same place : *TASK [Wait for the host to become non operational]*
After some time, it gave up and the deployment fails.
I don't know the reason for now, but I have seen this behavior in */etc/hosts *of the hypervisor.
In the beginning of the deployment the entry *192.168.2.104 engine01.example.local* is added, then sometime after that it's deleted, then a new entry is added with this IP *192.168.122.65 engine01.wodel.wd* which has nothing to do with the network I am using.
Here is the error I am seeing in the deployment log
2018-03-24 11:51:31,398+0100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:100 TASK [Wait for the host to become non operational] 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': u'name=hyperv01.wodel.wd', u'fetch_nested': False, u'nested_attributes': []}}, u'ansible_facts': {u'ovirt_hosts': []}} 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! => {"ansible_facts": {"ovirt_hosts": []}, "attempts": 150, "changed": false} 2018-03-24 12:02:07,587+0100 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:94 PLAY RECAP [engine01.wodel.wd] : ok: 15 changed: 8 unreachable: 0 skipped: 4 failed: 0 2018-03-24 12:02:07,688+0100 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:94 PLAY RECAP [localhost] : ok: 41 changed: 14 unreachable: 0 skipped: 3 failed: 1 2018-03-24 12:02:07,789+0100 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils.run:180 ansible-playbook rc: 2 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
2018-03-24 12:02:07,791+0100 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils.run:190 ansible-playbook stder r: 2018-03-24 12:02:07,792+0100 DEBUG otopi.context context._executeMethod:143 method exception Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/otopi/context.py", line 133, in _executeMethod method['method']() File "/usr/share/ovirt-hosted-engine-setup/scripts/../ plugins/gr-he-ansiblesetup/core/misc.py", line 186, in _closeup r = ah.run() File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_setup/ansible_utils.py", line 194, in run raise RuntimeError(_('Failed executing ansible-playbook')) RuntimeError: Failed executing ansible-playbook 2018-03-24 12:02:07,795+0100 ERROR otopi.context context._executeMethod:152 Failed to execute stage 'Closing up': Failed exec uting ansible-playbook
any idea????
Regards
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing listUsers@ovirt.orghttp://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
participants (3)
-
Andrei Verovski
-
Andy Michielsen
-
wodel youchi