[ovirt-users] hosted engine setup on second host fails

Stefan Wendler stefan.wendler at tngtech.com
Tue Sep 23 16:03:42 UTC 2014


On 09/23/2014 17:01, Itamar Heim wrote:
> On 09/23/2014 05:17 PM, Stefan Wendler wrote:
>> On 09/22/2014 10:52, Stefan Wendler wrote:
>>> On 09/19/2014 15:58, Itamar Heim wrote:
>>>> On 09/19/2014 03:32 PM, Stefan Wendler wrote:
>>>>> Hi there.
>>>>>
>>>>> I'm trying to install a hosted-engine on our second node (fist engine
>>>>> runs on node1).
>>>>>
>>>>> But I always get the message:
>>>>>
>>>>> [ ERROR ] Cannot automatically add the host to the Default cluster:
>>>>> Cannot add Host. Host with the same address already exists.
>>>>>
>>>>> I'm not entirely sure what I have to do when this message comes, so I
>>>>> just press ENTER:
>>>>>
>>>>> #######
>>>>> To continue make a selection from the options below:
>>>>>             (1) Continue setup - engine installation is complete
>>>>>             (2) Power off and restart the VM
>>>>>             (3) Abort setup
>>>>>
>>>>>             (1, 2, 3)[1]:
>>>>> ########
>>>>>
>>>>> Is there any other interaction required prior to selecting "1"?
>>>>>
>>>>> In the Web Gui I get the following message:
>>>>>
>>>>> X Adding new Host hosted_engine_2 to Cluster Default
>>>>>
>>>>> Here is the console output:
>>>>>
>>>>> # hosted-engine --deploy
>>>>> [ INFO  ] Stage: Initializing
>>>>>             Continuing will configure this host for serving as
>>>>> hypervisor
>>>>> and create a VM where you have to install oVirt Engine afterwards.
>>>>>             Are you sure you want to continue? (Yes, No)[Yes]:
>>>>> [ INFO  ] Generating a temporary VNC password.
>>>>> [ INFO  ] Stage: Environment setup
>>>>>             Configuration files: []
>>>>>             Log file:
>>>>> /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20140919141012-k2lag6.log
>>>>>
>>>>>
>>>>>             Version: otopi-1.2.3 (otopi-1.2.3-1.el6)
>>>>> [ INFO  ] Hardware supports virtualization
>>>>> [ INFO  ] Bridge ovirtmgmt already created
>>>>> [ INFO  ] Stage: Environment packages setup
>>>>> [ INFO  ] Stage: Programs detection
>>>>> [ INFO  ] Stage: Environment setup
>>>>> [ INFO  ] Stage: Environment customization
>>>>>
>>>>>             --== STORAGE CONFIGURATION ==--
>>>>>
>>>>>             During customization use CTRL-D to abort.
>>>>>             Please specify the storage you would like to use (nfs3,
>>>>> nfs4)[nfs3]:
>>>>>             Please specify the full shared storage connection path
>>>>> to use
>>>>> (example: host:/path): <some address>:/volume1
>>>>>             The specified storage location already contains a data
>>>>> domain.
>>>>> Is this an additional host setup (Yes, No)[Yes]?
>>>>> [ INFO  ] Installing on additional host
>>>>>             Please specify the Host ID [Must be integer, default: 2]:
>>>>>             The Host ID is already known. Is this a re-deployment
>>>>> on an
>>>>> additional host that was previously set up (Yes, No)[Yes]?
>>>>>
>>>>>             --== SYSTEM CONFIGURATION ==--
>>>>>
>>>>> [WARNING] A configuration file must be supplied to deploy Hosted
>>>>> Engine
>>>>> on an additional host.
>>>>>             The answer file may be fetched from the first host
>>>>> using scp.
>>>>>             If you do not want to download it automatically you can
>>>>> abort
>>>>> the setup answering no to the following question.
>>>>>             Do you want to scp the answer file from the first host?
>>>>> (Yes,
>>>>> No)[Yes]:
>>>>>             Please provide the FQDN or IP of the first host:
>>>>> <node1.domain>
>>>>>             Enter 'root' user password for host <node1.domain>:
>>>>> [ INFO  ] Answer file successfully downloaded
>>>>>
>>>>>             --== NETWORK CONFIGURATION ==--
>>>>>
>>>>>             The following CPU types are supported by this host:
>>>>>                    - model_Westmere: Intel Westmere Family
>>>>>                    - model_Nehalem: Intel Nehalem Family
>>>>>                    - model_Penryn: Intel Penryn Family
>>>>>                    - model_Conroe: Intel Conroe Family
>>>>>
>>>>>             --== HOSTED ENGINE CONFIGURATION ==--
>>>>>
>>>>>             Enter the name which will be used to identify this host
>>>>> inside
>>>>> the Administrator Portal [hosted_engine_2]:
>>>>>             Enter 'admin at internal' user password that will be used for
>>>>> accessing the Administrator Portal:
>>>>>             Confirm 'admin at internal' user password:
>>>>>    [ INFO  ] Stage: Setup validation
>>>>>
>>>>>             --== CONFIGURATION PREVIEW ==--
>>>>>
>>>>>             Engine FQDN                        : engine.domain
>>>>>             Bridge name                        : ovirtmgmt
>>>>>             SSH daemon port                    : 22
>>>>>             Gateway address                    : <some address>
>>>>>             Host name for web application      : hosted_engine_2
>>>>>             Host ID                            : 2
>>>>>             Image size GB                      : 25
>>>>>             Storage connection                 : <some
>>>>> address>:/volume1
>>>>>             Console type                       : vnc
>>>>>             Memory size MB                     : 8192
>>>>>             MAC address                        : 00:16:3e:3b:8d:66
>>>>>             Boot type                          : disk
>>>>>             Number of CPUs                     : 2
>>>>>             CPU Type                           : model_Westmere
>>>>>
>>>>>             Please confirm installation settings (Yes, No)[No]: yes
>>>>> [ ERROR ] Invalid value
>>>>>
>>>>>             Please confirm installation settings (Yes, No)[No]: Yes
>>>>> [ INFO  ] Stage: Transaction setup
>>>>> [ INFO  ] Stage: Misc configuration
>>>>> [ INFO  ] Stage: Package installation
>>>>> [ INFO  ] Stage: Misc configuration
>>>>> [ INFO  ] Configuring libvirt
>>>>> [ INFO  ] Configuring VDSM
>>>>> [ INFO  ] Starting vdsmd
>>>>> [ INFO  ] Waiting for VDSM hardware info
>>>>> [ INFO  ] Waiting for VDSM hardware info
>>>>> [ INFO  ] Connecting Storage Domain
>>>>> [ INFO  ] Configuring VM
>>>>> [ INFO  ] Updating hosted-engine configuration
>>>>> [ INFO  ] Stage: Transaction commit
>>>>> [ INFO  ] Stage: Closing up
>>>>>             To continue make a selection from the options below:
>>>>>             (1) Continue setup - engine installation is complete
>>>>>             (2) Power off and restart the VM
>>>>>             (3) Abort setup
>>>>>
>>>>>             (1, 2, 3)[1]:
>>>>> [ INFO  ] Engine replied: DB Up!Welcome to Health Status!
>>>>> [ ERROR ] Cannot automatically add the host to the Default cluster:
>>>>> Cannot add Host. Host with the same address already exists.
>>>>> [ INFO  ] Waiting for the host to become operational in the engine.
>>>>> This
>>>>> may take several minutes...
>>>>> [ INFO  ] Still waiting for VDSM host to become operational...
>>>>> [ INFO  ] Still waiting for VDSM host to become operational...
>>>>>
>>>>> And the stacktrace from the logs:
>>>>>
>>>>> 2014-09-19 14:14:07 DEBUG
>>>>> otopi.plugins.ovirt_hosted_engine_setup.engine.add_host
>>>>> add_host._closeup:438 Cannot add the host to the Default cluster
>>>>> Traceback (most recent call last):
>>>>>     File
>>>>> "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/ovirt-hosted-engine-setup/engine/add_host.py",
>>>>>
>>>>>
>>>>> line 432, in _closeup
>>>>>       override_iptables=True,
>>>>>     File
>>>>> "/usr/lib/python2.6/site-packages/ovirtsdk/infrastructure/brokers.py",
>>>>> line 9779, in add
>>>>>       headers={"Expect":expect, "Correlation-Id":correlation_id}
>>>>>     File
>>>>> "/usr/lib/python2.6/site-packages/ovirtsdk/infrastructure/proxy.py",
>>>>> line 88, in add
>>>>>       return self.request('POST', url, body, headers)
>>>>>     File
>>>>> "/usr/lib/python2.6/site-packages/ovirtsdk/infrastructure/proxy.py",
>>>>> line 118, in request
>>>>>       persistent_auth=self._persistent_auth)
>>>>>     File
>>>>> "/usr/lib/python2.6/site-packages/ovirtsdk/infrastructure/proxy.py",
>>>>> line 140, in __doRequest
>>>>>       persistent_auth=persistent_auth
>>>>>     File
>>>>> "/usr/lib/python2.6/site-packages/ovirtsdk/web/connection.py",
>>>>> line 134, in doRequest
>>>>>       raise RequestError, response
>>>>> RequestError:
>>>>> status: 409
>>>>> reason: Conflict
>>>>> detail: Cannot add Host. Host with the same address already exists.
>>>>> 2014-09-19 14:14:07 ERROR
>>>>> otopi.plugins.ovirt_hosted_engine_setup.engine.add_host
>>>>> add_host._closeup:445 Cannot automatically add the host to the Default
>>>>> cluster:
>>>>> Cannot add Host. Host with the same address already exists.
>>>>>
>>>>>
>>>>> Cheers,
>>>>> Stefan
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Users mailing list
>>>>> Users at ovirt.org
>>>>> http://lists.ovirt.org/mailman/listinfo/users
>>>>>
>>>>
>>>>
>>>> what type of hardware is this? check the host uuid is not the same on
>>>> both please.
>>>> http://lists.ovirt.org/pipermail/users/2014-September/027278.html
>>>
>>> Hi,
>>>
>>> this is Supermicro Hardware. But the uuids differ. Anyway, I regenerated
>>> the uuid on node2. But I first have to fix another problem. After a
>>> reboot the first engine on node1 doesn't start because it says the
>>> storage path cannot be found. arrgh
>>>
>>> I will investigate this and report my findings.
>>>
>>> Cheers,
>>> Stefan
>>>
>>> _______________________________________________
>>> Users mailing list
>>> Users at ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/users
>>
>> Well everything is up and running again but I still have the same
>> problem. I did a uuidgen > /etc/vdsm/vdsm.id on ovirt node 2 and 3 even
>> though the uuids were different already.
>>
>> What does ovirt mean by "Host with the same address already exists"?
>> What HOST is it referring to?
>>
>> Greetings,
>> Stefan
>>
> 
> oh, not same uuid, rather same host name (like ip address or dns name
> used to access it)
it - is the engine or the ovirt-node? The nodes have definitely
different ip addresses and dns entries. This is verified.

If it is the engine then I might have a problem understanding some
things I Basically want one engine that runs on each node, if needed.

Cheers



More information about the Users mailing list