Setting to invalid along the comment of Akihiro.
** Changed in: neutron
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1246525
Title:
Horizon displays floating IPs to allocate from unreachable external
networks of other tenants.
Status in OpenStack Dashboard (Horizon):
Expired
Status in neutron:
Invalid
Bug description:
Description of problem:
=======================
Horizon displays floating IPs to allocate from unreachable external networks
of other tenants.
Those pools are not reachable and cannot be used by a non related tenant.
Version-Release number of selected component (if applicable):
=============================================================
Grizzly, python-django-horizon-2013.1.4-1.el6ost.noarch
How reproducible:
=================
Always.
Steps to Reproduce:
===================
1. Have two tenants (admin tenant, test tenant)
2. Network for admin tenant:
- Create network named: internal with the subnet 192.168.1.0/24
- Create network named: external with the subnet 10.10.10.0/24 check
External Network in Admin tab for this network.
- Create Router named: Router1, Set gateway network: external
3. Network for demo tenant:
- Create network named: internal2 with the subnet 192.168.2.0/24
- Create network named: external2 with the subnet 11.11.11.0/24 check
External Network in Admin tab for this network.
- Create Router named: Router2, Set gateway network: external2
4. Launch an instance in admin tenant, attach the 'internal' network.
5. Associate Floating IP to that instance.
5. Click + and select the pool of the other tenant: external2.
6. Click Associate
Actual results:
===============
The IP address (11.11.11.x) suggested belongs to the other tenant pool:
external2, which shouldn't be accessible.
Association fails with the following error:
Error: External network d1e2a98f-0ee6-4192-bdd4-eb759456f059 is not
reachable from subnet 7e58ab9f-bac4-4544-af64-896c247542bd. Therefore,
cannot associate Port 60550899-a94a-44e2-a231-fe344f1d1838 with a
Floating IP.
Error: Unable to associate IP address 11.11.11.3.
Expected results:
=================
Only IPs allocated to the current tenant should be listed.
Additional Info:
================
I've yet to test if this reproduces in Havana.
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1246525/+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
