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, at 6:37 PM, Ruben S. Montero wrote: 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 can find a patch for this at [1] Cheers, and thanks for your feedback Ruben [1] http://dev.opennebula.org/projects/opennebula/repository/revisions/cabf3b417e62d87c9cfe465301e5cc6e6e5865b0/diff/src/lcm/LifeCycleStates.cc Link to issue: http://dev.opennebula.org/issues/1400 -- Ruben S. Montero, PhD Project co-Lead and Chief Architect OpenNebula - The Open Source Solution for Data Center Virtualization www.OpenNebula.org<http://www.OpenNebula.org/> | [email protected]<mailto:[email protected]> | @OpenNebula
_______________________________________________ Users mailing list [email protected] http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
