The broker was reported as down - I recall there was something about
'Failed to getVmStats' in the systemctl output. I wasn't sure how to
check the storage from the oVirt point of view (the GUI was
unavailable). When I put the bare metal engine back, it did take a
short while for the storage to bec
On Fri, Jun 30, 2017 at 10:34 AM, cmc wrote:
> Hi Denis,
>
> Yes, I did check that and it said it was out of global maintenance
> ('False' I think it said).
>
>
Did you check that the storage the hostedengine VM attaches to mounted and
is in a healthy state, and that the broker and agent services
Hello!
On Fri, Jun 30, 2017 at 5:34 PM, cmc wrote:
>
> Yes, I did check that and it said it was out of global maintenance
> ('False' I think it said).
>
>
Well, then it should start VM :-) Could you please share hosted-engine
--vm-status output? It may contain some interesting information
_
Hi Denis,
Yes, I did check that and it said it was out of global maintenance
('False' I think it said).
Thanks,
Cam
On Fri, Jun 30, 2017 at 4:31 PM, Denis Chaplygin wrote:
> Hello!
>
> On Fri, Jun 30, 2017 at 4:35 PM, cmc wrote:
>>
>> I restarted my 3 host cluster after setting it into global
Hello!
On Fri, Jun 30, 2017 at 4:35 PM, cmc wrote:
> I restarted my 3 host cluster after setting it into global maintenance
> mode and then shutting down all of the nodes and then bringing them up
> again. I moved it out of global maintenance mode and no VM is running,
> including the hosted eng
Hi,
I restarted my 3 host cluster after setting it into global maintenance
mode and then shutting down all of the nodes and then bringing them up
again. I moved it out of global maintenance mode and no VM is running,
including the hosted engine.
Any help greatly appreciated!
Thanks,
Cam
___
6 matches
Mail list logo