** Changed in: horizon
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1252403
Title:
Association targets of floating IP should be limited to reachable IP
from external network
Status in OpenStack Dashboard (Horizon):
Fix Released
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?
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1252403/+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
