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 become available (it is FC storage).
The agent did not report any errors in systemctl.

On Fri, Jun 30, 2017 at 4:39 PM, David Gossage
<dgoss...@carouselchecks.com> wrote:
>
>
> On Fri, Jun 30, 2017 at 10:34 AM, cmc <iuco...@gmail.com> 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 are running?
> Both have logs that may give some indication if it detects an issue as well.
>
>
>> Thanks,
>>
>> Cam
>>
>> On Fri, Jun 30, 2017 at 4:31 PM, Denis Chaplygin <dchap...@redhat.com>
>> wrote:
>> > Hello!
>> >
>> > On Fri, Jun 30, 2017 at 4:35 PM, cmc <iuco...@gmail.com> 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 engine.
>> >>
>> >> Any help greatly appreciated!
>> >
>> >
>> > Are you sure you are really out of global maintenance? Could you please
>> > post
>> > hosted-engine --vm-status output?
>> _______________________________________________
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>
>
_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Reply via email to