Is this still an issue? If so, please explain what the issue is in more detail - what is the user impact?
Conductor is now passing the migration record it creates down to the compute, so I don't think RT creates it anymore and this shouldn't be an issue. See: https://github.com/openstack/nova/commit/9868a4d9c1c3b705d328fc11bba634857cde0f2e ** Changed in: nova Status: In Progress => Invalid -- 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/1661793 Title: Should generate migration record after successfully claimed Status in OpenStack Compute (nova): Invalid Bug description: Currently the migration record was generated before successful claim, http://git.openstack.org/cgit/openstack/nova/tree/nova/compute/resource_tracker.py#n197 this may lead to an bad migration record if the claim failed afterwards and reschedule also failed. It could be better if we generate the migration records after successfully claimed. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1661793/+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