yahoo-eng-team team mailing list archive

[Yves-Gwenael Bourhis <yves-gwenael.bourhis@xxxxxxxxxxxxx>]

Public bug reported:

If the public network has router:external set, in in "Manage Floating IP
Associations" we can't find any ports to associate in horizon, while we
can in the neutron CLI

This happened after https://bugs.launchpad.net/horizon/+bug/1252403
NOTE: Using OpenContrail as backend where a network with router:external does not need to be shared (and sys admin does not want to share it) to prevent spawning VMs directly on the public network (but associating a FIP is allowed in policies).

** Affects: horizon
     Importance: Undecided
     Assignee: Yves-Gwenael Bourhis (yves-gwenael-bourhis)
         Status: In Progress

-- 
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/1462902

Title:
  Can't display port list on a router:external network in "Manage
  Floating IP Associations" page

Status in OpenStack Dashboard (Horizon):
  In Progress

Bug description:
  If the public network has router:external set, in in "Manage Floating
  IP Associations" we can't find any ports to associate in horizon,
  while we can in the neutron CLI

  This happened after https://bugs.launchpad.net/horizon/+bug/1252403
  NOTE: Using OpenContrail as backend where a network with router:external does not need to be shared (and sys admin does not want to share it) to prevent spawning VMs directly on the public network (but associating a FIP is allowed in policies).

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1462902/+subscriptions