[ovirt-users] Ovirt HC engine will not start

[Kasturi Narra]

Hi,

   In the agent.log file i see that it fails to connect to storage server.
Can you please check the following .

1) can you please check 'gluster peer status' and make sure that all the
nodes in the cluster are connected ?

2) can you gluster volume status <engine_volume> and make sure that at
least two of the bricks are online?

Thanks
kasturi

On Fri, Sep 15, 2017 at 12:29 PM, Jesper Andersson <
jesper.andersson at viconia.se> wrote:

> Hi.
>
> I have a HC environment (oVirt 4.1.4) where the engine does not start.
> Tryed to update it to the latest oVirt but something happend on the
> storage side.
> Seemed like there was no data on the second node so we did a full heal,
> restarted the environment and now the ha-agent, broker and the engine
> does not start.
> "The hosted engine configuration has not been retrieved from shared
> storage. Please ensure that ovirt-ha-agent is running and the storage
> server is reachable."
>
> Tried to start the ha-agent but receives this error:
> ovirt-ha-agent ovirt_hosted_engine_ha.agent.agent.Agent ERROR Traceback
> (most recent call last):
>   File
> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/agent.py",
> line 191, in _run_agent
>
> The broker wont start either:
> ovirt-ha-broker ovirt_hosted_engine_ha.broker.listener.ConnectionHandler
> ERROR Error handling request, data: 'set-storage-domain
> FilesystemBackend dom_type=glusterfs
> sd_uuid=2a79ea65-3df3-43cf-b1ba-304581f7918a'
> Traceback (most recent call last):
> File "/usr/lib/python2.7/site-packages/ovirt...
>
> I'm not that experienced with ovirt nor gluster storage but gluster
> seems OK as far as I can see.
> Does anyone have an idea of how to resolve this?
>
> Please see attached logs.
>
>
> _______________________________________________
> 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/20170918/e30f5bde/attachment.html>