<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Aug 29, 2016 at 4:08 PM, Alexis HAUSER <span dir="ltr"><<a href="mailto:alexis.hauser@telecom-bretagne.eu" target="_blank">alexis.hauser@telecom-bretagne.eu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Thank you for your explanations, this is very clear now :)<br>
<br>
<br>
<br>
Actually I was confused because "this host" is used in several different contexts, if I am right :<br>
<br>
1 - For the engine (which is not a host, but a guest) :<br>
<span class="">"Enter the name which will be used to identify this host inside the Administrator Portal [hosted_engine_2]"<br>
<br>
</span>2 - For the Host<br>
It asks the same things for the FQDN, but not for the engine this time, for the real "host"<br>
<br>
Please confirm me this, so I will know if I have to open a bug for this.<br>
<br>
<br></blockquote><div><br></div><div>No, in both the case it's referring to the host you are going to add to your engine (the host where you are running hosted-engine --deploy): the first one is a label to easily identify your host, the second one the address to reach it.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Now my error is the following :<br>
<br>
"[ ERROR ] Failed to execute stage 'Closing up': Specified cluster does not exist: Default"<br>
<br>
I think it assume I didn't change the name of the default cluster after deploying the first host. I will try to workaround with this by renaming the datacenter<br>
I will check if a bug if open on the bugzilla about this and if not I'll open one.<br>
<br>
<br>
<br>
<br>
<br>
----- Mail original -----<br>
De: "Simone Tiraboschi" <<a href="mailto:stirabos@redhat.com">stirabos@redhat.com</a>><br>
À: "Alexis HAUSER" <<a href="mailto:alexis.hauser@telecom-bretagne.eu">alexis.hauser@telecom-<wbr>bretagne.eu</a>><br>
Cc: "users" <<a href="mailto:users@ovirt.org">users@ovirt.org</a>><br>
Envoyé: Jeudi 25 Août 2016 16:56:17<br>
Objet: Re: [ovirt-users] 3.6 : Hosted engine High Availability<br>
<div class="HOEnZb"><div class="h5"><br>
On Thu, Aug 25, 2016 at 4:26 PM, Alexis HAUSER<br>
<<a href="mailto:alexis.hauser@telecom-bretagne.eu">alexis.hauser@telecom-<wbr>bretagne.eu</a>> wrote:<br>
><br>
>> Can you please share your hosted-engine-setup logs?<br>
><br>
> Yes of course, here they are :)<br>
<br>
OK, the issue is here:<br>
2016-08-25 12:49:04 DEBUG otopi.plugins.otopi.dialog.<wbr>human<br>
human.queryString:156 query OVESETUP_NETWORK_FQDN_HOST_<wbr>HOSTNAME<br>
2016-08-25 12:49:04 DEBUG otopi.plugins.otopi.dialog.<wbr>human<br>
dialog.__logString:219 DIALOG:SEND Please provide the<br>
address of this host.<br>
2016-08-25 12:49:04 DEBUG otopi.plugins.otopi.dialog.<wbr>human<br>
dialog.__logString:219 DIALOG:SEND Note: The engine VM<br>
and all the other hosts should be able to correctly resolve it.<br>
2016-08-25 12:49:04 DEBUG otopi.plugins.otopi.dialog.<wbr>human<br>
dialog.__logString:219 DIALOG:SEND Host address:<br>
[localhost.localdomain]:<br>
2016-08-25 12:49:37 DEBUG otopi.plugins.otopi.dialog.<wbr>human<br>
dialog.__logString:219 DIALOG:RECEIVE <a href="http://vm-rhemgr.mydomain.com" rel="noreferrer" target="_blank">vm-rhemgr.mydomain.com</a><br>
2016-08-25 12:49:37 DEBUG<br>
otopi.plugins.ovirt_hosted_<wbr>engine_setup.network.bridge<br>
hostname.test_hostname:411 test_hostname exception<br>
Traceback (most recent call last):<br>
File "/usr/lib/python2.7/site-<wbr>packages/ovirt_setup_lib/<wbr>hostname.py",<br>
line 407, in test_hostname<br>
not_local_text,<br>
File "/usr/lib/python2.7/site-<wbr>packages/ovirt_setup_lib/<wbr>hostname.py",<br>
line 252, in _validateFQDNresolvability<br>
fqdn=fqdn,<br>
RuntimeError: <a href="http://vm-rhemgr.mydomain.com" rel="noreferrer" target="_blank">vm-rhemgr.mydomain.com</a> did not resolve into an IP address<br>
2016-08-25 12:49:37 ERROR<br>
otopi.plugins.ovirt_hosted_<wbr>engine_setup.network.bridge<br>
dialog.queryEnvKey:115 Host name is not valid: <a href="http://vm-rhemgr.mydomain.com" rel="noreferrer" target="_blank">vm-rhemgr.mydomain.com</a><br>
did not resolve into an IP address<br>
<br>
<br>
<br>
'Please provide the address of THIS host.' means that you have to<br>
enter/validate the address of the host you are going to add (the host<br>
where you are running hosted-engine --deploy command).<br>
<br>
Let's try to recap:<br>
the fqdn of your engine VM is '<a href="http://vm-rhemgr.mydomain.com" rel="noreferrer" target="_blank">vm-rhemgr.mydomain.com</a>',<br>
the fqdn of your host is currently 'localhost.localdomain' but it's<br>
not acceptable (try to run 'ssh localhost.localdomain' on the engine<br>
VM and see where are you getting...)<br>
<br>
So you have just to configure a valid fqdn on your additional host<br>
(something like '<a href="http://my2ndhost.mydomain.com" rel="noreferrer" target="_blank">my2ndhost.mydomain.com</a>') and confirm it when asked by<br>
that question.<br>
<br>
Normally we suggest to rely on a properly configured DNS; you can just<br>
work entering values under '/etc/hosts' but it's up to you to properly<br>
maintain it:<br>
- the engine VM should be able to resolve the address of all the hosts<br>
to contact them: this is not true in your env, with<br>
'localhost.localdomain' your engine VM will not reach your host...<br>
- each host should be able to resolve the address of all the other<br>
hosts and also the address of the engine VM: this is not true in your<br>
env as I read 'RuntimeError: <a href="http://vm-rhemgr.mydomain.com" rel="noreferrer" target="_blank">vm-rhemgr.mydomain.com</a> did not resolve<br>
into an IP address'<br>
</div></div></blockquote></div><br></div></div>