Migrating VMs because previous host became non-operational

I'm seeing this error "Migrating VM blah-blah because previous host became non-operational. This appears in the WebUI under the task lists and is getting annoying since it disrupts things like creating snapshots. This migration is quite a feat on a single hosted engine installation with only one host so what exactly is going on? I'd be glad to include some logs and have looked at the vdsm logs but have no idea what I'm looking form.

On 30 May 2017, at 06:33, Brett Holcomb <biholcomb@l1049h.com> wrote:
I'm seeing this error "Migrating VM blah-blah because previous host became non-operational. This appears in the WebUI under the task lists and is getting annoying since it disrupts things like creating snapshots.
This migration is quite a feat on a single hosted engine installation with only one host so what exactly is going on? I'd be glad to include some logs and have looked at the vdsm logs but have no idea what I'm looking form.
Please start with engine.log And describe a bit more your exact environment, do you have only one host? Why did it became non-operational, is there any event message for that? Thanks, michal
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
participants (2)
-
Brett Holcomb
-
Michal Skrivanek