Reviewed: https://review.openstack.org/145269
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=48c24dbb6bc1e55973dce2b8bc3e74105b0020ce
Submitter: Jenkins
Branch: master
commit 48c24dbb6bc1e55973dce2b8bc3e74105b0020ce
Author: Matt Riedemann <mrie...@us.ibm.com>
Date: Tue Jan 6 09:11:24 2015 -0800
Return floating_ip['fixed_ip']['instance_uuid'] from neutronv2 API
The os-floating-ips extension translates the floating IP information
from the network API for the response but is only checking fields based
on what comes back from nova-network, which is using the FloatingIP
object. The neutronv2 API returns a different set of keys for the
instance/instance_uuid which the API extension doesn't handle and
therefore doesn't show the associated instance id for a given floating
IP.
The network APIs should return consistent data formats so this change
adds the expected key to fix the bug in the API extension (since the API
extensions shouldn't have to know the implementation details of the
network API, there are some extensions actually checking if it's the
neutron API and parsing the result set based on that).
This change will be used to backport the fix to the stable branches.
The longer term fix is to convert the neutronv2 get_floating_ip* API
methods to use nova objects which will be done as part of blueprint
kilo-objects in a separate change.
Closes-Bug: #1380965
Change-Id: I01df2096ced51eb9ebfd994cf8397f2fa094f6e3
** Changed in: nova
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1380965
Title:
Floating IPs don't have instance ids in Juno
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1380965/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
