[ovirt-users] Deploying selfhosted engine
Maton, Brett
matonb at ltresources.co.uk
Wed Sep 14 09:05:32 UTC 2016
Oops :)
hosted setup log attached.
On 14 September 2016 at 09:59, Simone Tiraboschi <stirabos at redhat.com>
wrote:
>
>
> On Wed, Sep 14, 2016 at 10:46 AM, Maton, Brett <matonb at ltresources.co.uk>
> wrote:
>
>> Log attached as request
>>
>>
> Sorry, I was asking for hosted-engine-setup logs; you can find them
> under /var/log/ovirt-hosted-engine-setup/
>
>
>> On 14 September 2016 at 08:48, Simone Tiraboschi <stirabos at redhat.com>
>> wrote:
>>
>>>
>>>
>>> On Wed, Sep 14, 2016 at 8:19 AM, Maton, Brett <matonb at ltresources.co.uk>
>>> wrote:
>>>
>>>>
>>>> I'm having trouble deploying selfhosted engine following this guide
>>>> http://www.ovirt.org/develop/developer-guide/engine/migrate-
>>>> to-hosted-engine/
>>>>
>>>> It gets close to deploying the vm, but fails with
>>>>
>>>> 2016-09-13 19:46:04 ERROR otopi.plugins.gr_he_common.core.misc
>>>> misc._terminate:180 Hosted Engine deployment failed: this system is not
>>>> reliable, please check the issue,fix and redeploy
>>>>
>>>
>>> can you please attach the whole log to let us check where it's failing?
>>>
>>>
>>>>
>>>> For storage I chose a random NFS share on a remote host that was empty,
>>>> I did notice that something kept removing 'nameserver' entries from
>>>> resolv.conf
>>>>
>>>> vdsm log show issues connecting to the broker,
>>>>
>>>
>>> ovirt-hosted-engine-setup will enable and start the broker if and only
>>> if the deployment went fine; that errors at deploy time are harmless since
>>> the broker is really down.
>>>
>>>
>>>>
>>>> periodic/0::ERROR::2016-09-13 19:49:49,704::brokerlink::75::
>>>> ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink::(connect) Failed to
>>>> connect to broker, the number of errors has exceeded the limit (1)
>>>> periodic/0::ERROR::2016-09-13 19:49:49,704::api::253::root::(_getHaInfo)
>>>> failed to retrieve Hosted Engine HA info
>>>> periodic/1::WARNING::2016-09-13 19:49:49,748::periodic::269::v
>>>> irt.periodic.VmDispatcher::(__call__) could not run <class
>>>> 'vdsm.virt.periodic.DriveWatermarkMonitor'> on
>>>> [u'1ed592d3-2b69-4901-9ff6-fe21d1dff8c5']
>>>> periodic/2::WARNING::2016-09-13 19:49:51,749::periodic::269::v
>>>> irt.periodic.VmDispatcher::(__call__) could not run <class
>>>> 'vdsm.virt.periodic.DriveWatermarkMonitor'> on
>>>> [u'1ed592d3-2b69-4901-9ff6-fe21d1dff8c5']
>>>> periodic/3::WARNING::2016-09-13 19:49:53,749::periodic::269::v
>>>> irt.periodic.VmDispatcher::(__call__) could not run <class
>>>> 'vdsm.virt.periodic.DriveWatermarkMonitor'> on
>>>> [u'1ed592d3-2b69-4901-9ff6-fe21d1dff8c5']
>>>> periodic/0::WARNING::2016-09-13 19:49:55,750::periodic::269::v
>>>> irt.periodic.VmDispatcher::(__call__) could not run <class
>>>> 'vdsm.virt.periodic.DriveWatermarkMonitor'> on
>>>> [u'1ed592d3-2b69-4901-9ff6-fe21d1dff8c5']
>>>> periodic/1::WARNING::2016-09-13 19:49:57,750::periodic::269::v
>>>> irt.periodic.VmDispatcher::(__call__) could not run <class
>>>> 'vdsm.virt.periodic.DriveWatermarkMonitor'> on
>>>> [u'1ed592d3-2b69-4901-9ff6-fe21d1dff8c5']
>>>> periodic/2::WARNING::2016-09-13 19:49:59,751::periodic::269::v
>>>> irt.periodic.VmDispatcher::(__call__) could not run <class
>>>> 'vdsm.virt.periodic.DriveWatermarkMonitor'> on
>>>> [u'1ed592d3-2b69-4901-9ff6-fe21d1dff8c5']
>>>>
>>>> What should I check next ?
>>>>
>>>> _______________________________________________
>>>> Users mailing list
>>>> Users at ovirt.org
>>>> http://lists.ovirt.org/mailman/listinfo/users
>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20160914/7a2d14b5/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ovirt-hosted-engine-setup.tgz
Type: application/x-gzip
Size: 42547 bytes
Desc: not available
URL: <http://lists.ovirt.org/pipermail/users/attachments/20160914/7a2d14b5/attachment-0001.tgz>
More information about the Users
mailing list