Public bug reported: Shown in a tempest test here:
http://logs.openstack.org/95/356095/2/check/gate-tempest-dsvm-neutron- full-ubuntu-xenial/8d3cbb2/console.html#_2016-08-18_03_18_38_290951 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://review.openstack.org/#/c/351960/. Basically the problem is that this method isn't decorated with the refresh_cache decorator: https://github.com/openstack/nova/blob/d14fc79f65e04cc39a3988783344aecd84621291/nova/network/neutronv2/api.py#L1826 But notice that this is: https://github.com/openstack/nova/blob/d14fc79f65e04cc39a3988783344aecd84621291/nova/network/neutronv2/api.py#L1845 That's the method that's called from the REST API when disassociating, but not deleting, a floating IP from a server. ** Affects: nova Importance: Medium Assignee: MJWurtz (michael-wurtz) Status: Triaged ** Affects: nova/liberty Importance: Medium Status: Confirmed ** Affects: nova/mitaka Importance: Medium Status: Confirmed ** Tags: low-hanging-fruit neutron ** Also affects: nova/mitaka Importance: Undecided Status: New ** Also affects: nova/liberty Importance: Undecided Status: New ** Changed in: nova/mitaka Status: New => Confirmed ** Changed in: nova/liberty Status: New => Confirmed -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1614538 Title: neutron: instance.info_cache isn't refreshed after deleting associated floating IP Status in OpenStack Compute (nova): Triaged Status in OpenStack Compute (nova) liberty series: Confirmed Status in OpenStack Compute (nova) mitaka series: Confirmed Bug description: Shown in a tempest test here: http://logs.openstack.org/95/356095/2/check/gate-tempest-dsvm-neutron- full-ubuntu-xenial/8d3cbb2/console.html#_2016-08-18_03_18_38_290951 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://review.openstack.org/#/c/351960/. Basically the problem is that this method isn't decorated with the refresh_cache decorator: https://github.com/openstack/nova/blob/d14fc79f65e04cc39a3988783344aecd84621291/nova/network/neutronv2/api.py#L1826 But notice that this is: https://github.com/openstack/nova/blob/d14fc79f65e04cc39a3988783344aecd84621291/nova/network/neutronv2/api.py#L1845 That's the method that's called from the REST API when disassociating, but not deleting, a floating IP from a server. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1614538/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
