summaryrefslogtreecommitdiff
path: root/devstack
diff options
context:
space:
mode:
authorMatt Riedemann <mriedem.os@gmail.com>2019-04-30 17:45:32 -0400
committerMatt Riedemann <mriedem.os@gmail.com>2019-09-06 16:09:23 +0000
commit481cb5ce04e220c26e5772f4253d63e212adca45 (patch)
treeb99e358c272aa36e854b5847b90b639af14b6255 /devstack
parent9cbedea0bf5535fc45d78c80e6d7499512e4c5f5 (diff)
downloadnova-481cb5ce04e220c26e5772f4253d63e212adca45.tar.gz
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
Diffstat (limited to 'devstack')
-rw-r--r--devstack/nova-multi-cell-blacklist.txt3
1 files changed, 0 insertions, 3 deletions
diff --git a/devstack/nova-multi-cell-blacklist.txt b/devstack/nova-multi-cell-blacklist.txt
index 87f07be426..afda00fae1 100644
--- a/devstack/nova-multi-cell-blacklist.txt
+++ b/devstack/nova-multi-cell-blacklist.txt
@@ -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