Red Hat Bugzilla – Bug 1187992
[Horizon] Fix display of ports when associating floating IP
Last modified: 2016-04-26 11:06:28 EDT
Description of problem: It's impossible to associate a floating IP to a port of an instance. This happens when the gateway router is not in the same tenant as the instance, but still attached to a network shared across tenants -- because we were only considering ports in our tenant to find gateway routers that are reachable. See upstream bugs: - https://bugs.launchpad.net/horizon/+bug/1252403 - https://bugs.launchpad.net/horizon/+bug/1394051
The direction of the fix is currently under discussion. It's more the discussion to revert the change introducing this here; From outside, the result is quite comparable. From comments, it's currently broken only for admin users, where it previously was broken for all users.
This review should fix that issue as well. https://review.openstack.org/#/c/163728/
As part of https://review.openstack.org/#/c/165994/ ,this was merged to juno on Apr 17, 2015 10:47 AM, unfortunately, that was after tagging 2014.2.3 I will look into cherry-picking this
Verified ========= python-django-horizon-2014.2.3-6.1.el7ost.noarch
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2015-1679.html