[ovirt-users] Failed to start self hosted engine after upgrading oVirt to 4.0

Simone Tiraboschi stirabos at redhat.com
Tue Jun 28 10:08:51 EDT 2016


On Tue, Jun 28, 2016 at 3:02 PM, Dan Kenigsberg <danken at redhat.com> wrote:
> On Mon, Jun 27, 2016 at 10:08:33AM +0200, Stefano Danzi wrote:
>> Hi!
>
>
> Thanks for the detailed logging!
>
>>
>> The broker error is:
>>
>> ==> /var/log/ovirt-hosted-engine-ha/agent.log <==
>> MainThread::INFO::2016-06-27 09:27:03,311::brokerlink::140::ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink::(start_monitor)
>> Success, id 140293563619152
>>
>> ==> /var/log/ovirt-hosted-engine-ha/broker.log <==
>> Thread-25::ERROR::2016-06-27 09:27:03,314::listener::182::ovirt_hosted_engine_ha.broker.listener.ConnectionHandler::(handle)
>> Error while serving connection
>> Traceback (most recent call last):
>>   File
>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/broker/listener.py",
>> line 166, in handle
>>     data)
>>   File
>> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/broker/listener.py",
>> line 299, in _dispatch
>>     .set_storage_domain(client, sd_type, **options)
>>   File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/broker/storage_broker.py",
>> line 66, in set_storage_domain
>>     self._backends[client].connect()
>>   File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/storage_backends.py",
>> line 400, in connect
>>     volUUID=volume.volume_uuid
>>   File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/storage_backends.py",
>> line 245, in _get_volume_path
>>     volUUID
>
> We have two issues here. First is that
> https://gerrit.ovirt.org/gitweb?p=ovirt-hosted-engine-ha.git;a=blob;f=ovirt_hosted_engine_ha/lib/storage_backends.py;h=f2fbdc43d0e4afd7539a3a1de75de0cb07bdca9d;hb=HEAD#l271
> is still using vdscli to contact vdsm, instead of the preferred
> jsonrpccli.

We already have this one:
https://bugzilla.redhat.com/show_bug.cgi?id=1101554

> The second is that vdscli.connect's heuristic ends up reading the local
> server address from vdsm config, where it finds the default ipv6-local
> address of "::".
>
> Please try setting
>
> [addresses]
> management_ip='0.0.0.0'
>
> in your /etc/vdsm/vdsm.conf instead of the crontab hacks.
>
>
> Would you please open a bug about the two issues
> (ovirt-hosted-engine-ha and vdsm networking)?
>
> Would you report the output of `netstats -nltp` on your host, as I do
> not completely understand why no interface (not even the loopback one)
> was listening on ipv6?
>
> Regards,
> Dan.


More information about the Users mailing list