Red Hat Bugzilla – Bug 1313922
If moving engine vm due to big score diff, should migrate instead of shutdown/startup
Last modified: 2016-03-03 05:49:29 EST
Description of problem:
$subject. I see this in agent.log:
MainThread::ERROR::2016-02-23 15:12:17,511::states::385::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(consume) Host didi-box1.home.local (id 3) score is significantly better than local score, shutting down VM on this host
Briefly looked at the code, can't see that we try to migrate.
This behavior is intentional. Big score difference might mean that the network is slow or the host is too loaded and it would take too long time to safely migrate the VM. So we shut it down and restart it on different node.
Thanks for the explanation.
Is there an official way to prevent that?
In particular, when upgrading the first host in a 3.5 cluster to 3.6, this will always happen, as the new host will have score 3400 and the 3.5 ones 2400. I'd find it pretty harsh for a vm do go down if the only reason is that a host was upgraded...
Sure, put the cluster into global maintenance. That will disable all automation during the upgrade.