Comment 5 for bug 1550400
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Change abandoned on neutron (master) | #5 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
2eb648a
demo site
(Get the code!)
Change abandoned by Andreas Scheuring (<email address hidden>) on branch: master
Review: https:/
Reason: This patch series does achieve the desired behavior.
#1 Port binding happens after the Live Migration already succeeded. If portbinding fail, the port will stay in Build state, but the instance has migrated before. It will not be rolled back.
#2 If the scheduler reschedules an instance to another host (as the first host could not start the instance due to some error), the porbinding also contains the .original port. So just having the .orginal port present in the port context is not sufficient to detect an migration.