yahoo-eng-team team mailing list archive

[Eugene Nikanorov <enikanorov@xxxxxxxxxxxx>]

This puts another consistency question: what if, even if we validate tenant_id when creating a quota, it is removed afterwards?
It's still an inconsistency.

I don't think it makes sense to do anything about it at this point.
Quota API is for admins, so it think it's a fair bit of system knowledge that is required to operate quotas.

** Changed in: neutron
       Status: New => Opinion

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1398992

Title:
  quota-update succeeds for nonexistent tenant_id

Status in OpenStack Neutron (virtual network service):
  Opinion

Bug description:
  Possibly related to https://bugs.launchpad.net/neutron/+bug/1307506

  Issue a CLI request to update the quota for a nonexistent tenant_id
  (not in keystone tenant-list).

  The update succeeds and "neutron quota-list" gets a new entry for
  tenant_id foo.

  $ neutron quota-update --tenant_id foo --port 75
  +---------------------+-------+
  | Field               | Value |
  +---------------------+-------+
  | floatingip          | 50    |
  | network             | 10    |
  | port                | 75    |
  | router              | 10    |
  | security_group      | 10    |
  | security_group_rule | 100   |
  | subnet              | 10    |
  +---------------------+-------+

  Expected behavior: The CLI (at the very least) or neutron (at most)
  would prevent this from succeeding.

  Pardon the whitespace mangling. Can't be helped:
  https://bugs.launchpad.net/launchpad/+bug/2627

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