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