← Back to team overview

yahoo-eng-team team mailing list archive

  1. yahoo-eng-team team
  2. Mailing list archive
  3. Message #41865

[Bug 1520071] [NEW] When updating the floating IP quota, compared value is of logged in user

  Thread Previous • Date Previous • • Thread Next 
Public bug reported:

I've run into this bug with nova-network. I'm not sure if this affects
Neutron, too.

When I update a user's quota through Horizon, Horizon will first obtain
the user's usage and ensure that the value being set is greater than
what the user is currently using.  I believe this happens at

openstack_dashboard/dashboards/identity/projects/workflows.py

during "def clean".

The problem, though, is that the Floating IP usage being reported is of
the logged in user. In my case: "admin". I can see this in the debug
logs:

DEBUG:urllib3.connectionpool:"GET /v2/admin-tenant-id/os-floating-ips
HTTP/1.1" 200 None

It doesn't look like "os-floating-ips" takes a "tenant-id" parameter to
see the usage of another tenant.

The result of this bug is that I'm unable to set a user's floating IPs
when the admin user is using more floating IPs than what I'm trying to
set for the user.

** 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/1520071

Title:
  When updating the floating IP quota, compared value is of logged in
  user

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  I've run into this bug with nova-network. I'm not sure if this affects
  Neutron, too.

  When I update a user's quota through Horizon, Horizon will first
  obtain the user's usage and ensure that the value being set is greater
  than what the user is currently using.  I believe this happens at

  openstack_dashboard/dashboards/identity/projects/workflows.py

  during "def clean".

  The problem, though, is that the Floating IP usage being reported is
  of the logged in user. In my case: "admin". I can see this in the
  debug logs:

  DEBUG:urllib3.connectionpool:"GET /v2/admin-tenant-id/os-floating-ips
  HTTP/1.1" 200 None

  It doesn't look like "os-floating-ips" takes a "tenant-id" parameter
  to see the usage of another tenant.

  The result of this bug is that I'm unable to set a user's floating IPs
  when the admin user is using more floating IPs than what I'm trying to
  set for the user.

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

Follow ups

  Thread Previous • Date Previous • • Thread Next