Thank you very much, this is exactly the same case than me.
With 'echo c >/proc/sysrq-trigger' it worked as expected.
Let's see how the bug resolution evolves.
Felip Moll Marquès
Computer Science Engineer
E-Mail - lip...@gmail.com
WebPage - http://lipix.ciutadella.es
2016-10-11 11:37 GMT+02:00 Simone Tiraboschi <stira...@redhat.com>:
> On Tue, Oct 11, 2016 at 11:28 AM, Felip Moll <lip...@gmail.com> wrote:
>> I have latest version of ovirt 4 installed on a Centos 7, 2 hypervisor
>> nodes (rdkvm[1-2]) and 1 ovirt-engine node (rdhead1).
>> GlusterFS is setup with 2 bricks on both rdkvm1 and rdkvm2.
>> I have some vm's running on the infraestructure. I have HA enabled and
>> ipmi is working.
>> I manually poweroff force one node. Then I expect that VM's running on
>> that node are started in the remaining node because of the HA setting.
>> What happens is that ovirt starts the powered off node but not the
>> vm's that remain shutted down.
>> Is it the correct behaviour? How can I make that vm's are auto-started
>> if they were running before hypervisor kill?
> No, but it's a know issue:
> The issue is that if you properly shut down the host, for some reason also
> the VMs there will be properly shutdown (or at least we are detecting it
> like that) and so the HA mechanism will not restart them thinking that it
> was a voluntary shutdown triggered by the user.
> It should properly work if you simply disconnect the network from the test
> host: the host should be fenced and the HA VM restarted somewhere else.
> Please see also:
>> Felip M
>> Felip Moll Marquès
>> Computer Science Engineer
>> E-Mail - lip...@gmail.com
>> WebPage - http://lipix.ciutadella.es
>> Users mailing list
Users mailing list