yahoo-eng-team team mailing list archive

["massimo.sgaravatto" <massimo.sgaravatto@xxxxxxxxx>]

Public bug reported:

Environment: OpenStack Mitaka on CentOS 7 (but I see the same issue also
on a Kilo installation)

I have an external network, and a network for each project.
The external network belongs to the 'admin' project.
Each project network belongs to the relevant project.
There is a single router, belonging to the 'admin' project, connecting the external network and all the project networks.

In such environment, a user (without admin role) belonging to a specific project, can't associate a floating IP to an instance using the dashboard: the error message is 'no ports available'.
The floating ip association works using the "nova floating-ip-associate " command line tool.

** Affects: horizon
     Importance: Undecided
         Status: New

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

Title:
  "No ports available" when associating a floating IP to an instance
  when the router belongs to another project

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  Environment: OpenStack Mitaka on CentOS 7 (but I see the same issue
  also on a Kilo installation)

  I have an external network, and a network for each project.
  The external network belongs to the 'admin' project.
  Each project network belongs to the relevant project.
  There is a single router, belonging to the 'admin' project, connecting the external network and all the project networks.

  In such environment, a user (without admin role) belonging to a specific project, can't associate a floating IP to an instance using the dashboard: the error message is 'no ports available'.
  The floating ip association works using the "nova floating-ip-associate " command line tool.

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