neutron: instance.info_cache isn't refreshed after deleting associated floating IP
Bug #1614538 reported by
Matt Riedemann
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
MJWurtz | ||
Liberty |
Fix Released
|
Medium
|
Vijay | ||
Mitaka |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Shown in a tempest test here:
You can see from this patch that we refresh the instance's network info_cache (server.addresses) when deleting a floating IP associated with that instance but only when using nova-network, we don't do it for neutron.
This is related to bug 1586931 and investigation that happened in https:/
Basically the problem is that this method isn't decorated with the refresh_cache decorator:
But notice that this is:
That's the method that's called from the REST API when disassociating, but not deleting, a floating IP from a server.
To post a comment you must log in.
Once this is fixed in nova we can land a tempest test to continue to verify this behavior in the API.