Association targets of floating IP should be limited to reachable IP from external network
Bug #1252403 reported by
Kevin Fox
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Dashboard (Horizon) |
Fix Released
|
Medium
|
Akihiro Motoki |
Bug Description
I often create vm's with one public network interface (network with a router), and one or more private interfaces (IE, network without router). When adding a floating ip to one of these instances, it randomly picks one of the ip's and it is a pain to find the other one in the ui when it is wrong.
I believe a floating ip can only be attached when there is a router on the network. If so, can Horizon filter out all the ip address options that do not have a router associated with them?
tags: | added: neutron |
Changed in horizon: | |
milestone: | none → next |
status: | New → Confirmed |
information type: | Public → Public Security |
information type: | Public Security → Public |
Changed in horizon: | |
status: | Fix Committed → Fix Released |
Changed in horizon: | |
milestone: | juno-rc1 → 2014.2 |
To post a comment you must log in.
Hi Kevin,
Could you please tell me how to reproduce this bug