Reviewed: https://review.openstack.org/318832 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e5b8060c08bb972a1960575749f240d7160bc114 Submitter: Jenkins Branch: master
commit e5b8060c08bb972a1960575749f240d7160bc114 Author: Dan Smith <[email protected]> Date: Thu May 19 11:00:17 2016 -0700 Completed migrations are not "in progress" This fixes an issue where we consider migrations that have been completed as "in progress" by not filtering them out of the result set from migration_get_in_progress_by_host_and_node(). This adds that state to the list and adds a migration in that state to the test case. If it is not filtered, the counts won't line up and the test will fail. Change-Id: I7aafab9abdbfafe9479846f06068ba8a963d290a Closes-Bug: #1583720 ** 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/1583720 Title: "Migration instance not found" is logged repeatedly to nova- compute.log after an instance was deleted Status in OpenStack Compute (nova): Fix Released Bug description: After migrating an instance and then deleting the instance, a migration record of status "completed" is not filtered from a query of in-progress migrations. This causes the following to be logged periodically forever: 2016-04-24 21:19:39.652 24323 DEBUG nova.compute.resource_tracker [req-...] Migration instance not found: Instance 585ac641-... could not be found. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1583720/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
