Find instance in another cell during floating IP re-association
When associating a floating IP to instance A but it was already associated with instance B, we try to refresh the info cache on instance B. The problem is the context is targeted to the cell for instance A and instance B might be in another cell, so we'll get an InstanceNotFound error trying to lookup instance B. This change tries to find the instance in another cell using its instance mapping, and makes the code a bit more graceful if instance B is deleted. Change-Id: I71790afd0784d98050ccd7cc0e046321da249cbe Closes-Bug: #1826472
This commit is contained in:
3 changed files with 221 additions and 8 deletions
@@ -4,6 +4,3 @@
# Exclude tempest.scenario.test_network tests since they are slow and
# only test advanced neutron features, unrelated to multi-cell testing.
^tempest.scenario.test_network
# Disable associate floating IP tests until bug 1826472 is fixed.
tempest.api.compute.floating_ips.test_floating_ips_actions.FloatingIPsAssociationTestJSON
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.