© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
4d1350f
(Get the code!)
I think this was the scenario described in IRC for this bug:
1. launch instance, it's in az zone-r7
2. shelve the instance
3. unshelve the instance - the scheduler now puts it in zone-r2
4. add a fixed IP to the instance
This fails because the addFixedIP flow is looking up ports for the instance by it's current zone and fails to find any because the ports still have the old zone in their device_owner field.
Looking at shelve offload, we could cleanup the device_owner and port binding information here:
https:/
That cleanup_
If we look at unshelve, we call this method to update the port bindings for the host to point at the new host:
https:/
That gets into this code to change the port's binding:host_id value to the new host after the unshelve:
https:/
At that point, we likely should also change the device_owner on the port, like is done here:
https:/