Reviewed: https://review.openstack.org/235994 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=89b1fecce116bc44f558e76cbb5dc43497ea67cc Submitter: Jenkins Branch: master
commit 89b1fecce116bc44f558e76cbb5dc43497ea67cc Author: Pawel Koniszewski <pawel.koniszew...@intel.com> Date: Mon Feb 1 11:56:59 2016 +0100 Update instance host in post live migration even when exception occurs Currently when, e.g., port binding fails on destination host nova loses track of running VM. Operator needs to change record in DB manually in order to recover VM in nova and then perform operations on destination host to repair such VM. Because VM is on destination host already it should be updated regardless of post live migration at destination result. Change-Id: Ibb5158f453abd9717e6d2ab501295351ca9d0dcf Closes-Bug: #1379581 ** Changed in: nova Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1379581 Title: live migration (block migration) fails at post_live_migration_at_destination function, but the status of this instance is still "migrating". Status in OpenStack Compute (nova): Fix Released Bug description: I have two compute node, host opencos114-93 and host opencos179-24. A migration failed at function of " post_live_migration_at_destination", but the status of this instance is still migrating. Log is as follows: http://paste.openstack.org/show/121143/ To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1379581/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp