Thanks for looking into the details Ruben. I figured out later that the
migration was failing because of last migration reason being 'none'. I resolved
this issue by deleting last migration records from 'history' and 'vm_pool'
tables. I will try out the patch soon.
--
Shantanu
On Aug 2, 2012,
Hi,
It seems that after a migration fail, that last history record was not
updated in the DB. If OpenNebula is restarted (or the VM flushed from
memory) that record will be restored with the last available REASON, that
was none. This, as reported, prevents the VM from being migrated again.
You ca
Hi
Your VM has reached and inconsistent state. Probably because of a bug. The
reason because OpenNebula refuses to migrate your VM is this history record:
3kvm-04 none 07/31 12:33:13 00 21:40:10 00 00:00:00
As you see there is a previous host (kvm-04) without any migration reason
s
I am getting following error while trying to migrate a VM:
{{{
$ onevm livemigrate 30 kvm-04
[VirtualMachineMigrate] Wrong state to perform action
}}}
The VM is not really in wrong 'state', but it failed to migrate during first
migration attempt because of connection (name resolution) issue.
