This might be working as designed, from what I can tell. Nova starts
building the nw_info cache list from the ports, so nova goes
ports->subnets->fixed_ips->floating_ips. I'm not sure if or how we
should change the nw info cache to represent this differently.
Note that listing the floating IPs via the nova API is correct, it shows
the associated server and public network:
stack@test:~$ nova floating-ip-list
+--------------------------------------+------------+--------------------------------------+----------+--------+
| Id | IP | Server Id
| Fixed IP | Pool |
+--------------------------------------+------------+--------------------------------------+----------+--------+
| 3a177df2-dd55-4b84-8cb6-68e9c747c14b | 172.24.4.5 |
f9bc7b39-ce32-4989-8fda-2d8f21e6532f | 10.0.0.3 | public |
+--------------------------------------+------------+--------------------------------------+----------+--------+
And when listing interfaces, it only shows the port and it's fixed IPs:
stack@test:~$ nova interface-list floating-test-1
+------------+--------------------------------------+--------------------------------------+---------------------------------------------+-------------------+
| Port State | Port ID | Net ID
| IP addresses | MAC Addr |
+------------+--------------------------------------+--------------------------------------+---------------------------------------------+-------------------+
| ACTIVE | 8f3feade-402c-49fc-8068-6a294f975b9e |
39702d92-27b7-4b4b-b62e-4980f9d8f59e |
10.0.0.3,fd89:5721:7b:0:f816:3eff:fe0f:2679 | fa:16:3e:0f:26:79 |
+------------+--------------------------------------+--------------------------------------+---------------------------------------------+-------------------+
Which are on the private network.
** Changed in: nova
Status: Confirmed => Invalid
--
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/1573142
Title:
proxied neutron network information is incorrect/confusing
Status in OpenStack Compute (nova):
Invalid
Bug description:
The information in the addresses dict for a server with a neutron
floating ip is misleading. Here is an example:
'addresses': {u'openstackci-network1': [{u'OS-EXT-IPS-MAC:mac_addr':
u'fa:16:3e:d7:d1:c2',
u'OS-EXT-IPS:type': u'fixed',
u'addr': u'10.0.1.24',
u'version': 4},
{u'OS-EXT-IPS-MAC:mac_addr':
u'fa:16:3e:d7:d1:c2',
u'OS-EXT-IPS:type': u'floating',
u'addr': u'172.99.106.118',
u'version': 4}]},
This is incorrect. The neutron networks on this cloud are:
| 405abfcc-77dc-49b2-a271-139619ac9b26 | openstackjenkins-network1 |
a47910bc-f649-45db-98ec-e2421c413f4e 10.0.1.0/24 |
| 7004a83a-13d3-4dcd-8cf5-52af1ace4cae | GATEWAY_NET |
cf785ee0-6cc9-4712-be3d-0bf6c86cf455 |
The floating IP does not come from openstackci-network1 - it comes from
GATEWAY_NET. But in the nova addresses dict, the floating IP is showing up as a
member of the list of addresses from openstackci-network1. It should really
look like this:
'addresses': {u'openstackci-network1': [{u'OS-EXT-IPS-MAC:mac_addr':
u'fa:16:3e:d7:d1:c2',
u'OS-EXT-IPS:type': u'fixed',
u'addr': u'10.0.1.24',
u'version': 4}],
{u'GATEWAY_NET': [{u'OS-EXT-IPS-MAC:mac_addr':
u'fa:16:3e:d7:d1:c2',
u'OS-EXT-IPS:type': u'floating',
u'addr': u'172.99.106.118',
u'version': 4}]},
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1573142/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
