yahoo-eng-team team mailing list archive

[melanie witt <1449498@xxxxxxxxxxxxxxxxxx>]

It looks like this is a request for enhancement for user validation
before showing/updating quota.

In Pike, we had a similar feature for validating the project [1] but
that will only handle a deleted project, not a user deleted from a valid
project.

If there is interest and someone willing to work on adding user
validation, they should send email to openstack-dev@xxxxxxxxxxxxxxxxxxx
with the tag "[nova]" and bring up this topic and then write a nova spec
to propose the change.

[1] https://blueprints.launchpad.net/nova/+spec/validate-project-with-
keystone

** Changed in: nova
       Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1449498

Title:
  the command “nova quota-show” Should not display  the  quota of a user
  has been deleted

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  1.version：icehouse
  2.Reproduce steps:
  （example）
  I create a tenant called bug_test
  then I cretaed two users called test1 and test2 which belong tenant bug_test
  [root@njq002 ~(keystone_admin)]# keystone tenant-list
  +----------------------------------+----------+---------+
  |                id                |   name   | enabled |
  +----------------------------------+----------+---------+
  | 6485ffa6b1f448919f00acab23207018 |  admin   |   True  |
  | c93d944ee63a45e0880161608e62eb83 | bug_test |   True  |
  | dc09e51878b54448b6ed39522295bb5a | services |   True  |
  +----------------------------------+----------+---------+
  [root@njq002 ~(keystone_admin)]# keystone user-list --tenant bug_test
  +----------------------------------+-------+---------+-------+
  |                id                |  name | enabled | email |
  +----------------------------------+-------+---------+-------+
  | 91c422e673ad4c399aace18ba5c4f049 | test1 |   True  |       |
  | be4fb020ae8b4001afb1797d81a3d903 | test2 |   True  |       |
  +----------------------------------+-------+---------+-------+

  then I  use “nova quota-update” change user test2's quota like this：

  [root@njq002 ~(keystone_admin)]# nova quota-update c93d944ee63a45e0880161608e62eb83 --user be4fb020ae8b4001afb1797d81a3d903 --instances 8
  [root@njq002 ~(keystone_admin)]# nova quota-show  --tenant  c93d944ee63a45e0880161608e62eb83 --user be4fb020ae8b4001afb1797d81a3d903
  +-----------------------------+-------+
  | Quota                       | Limit |
  +-----------------------------+-------+
  | instances                   | 8     |
  | cores                       | 20    |
  | ram                         | 51200 |
  | floating_ips                | 10    |
  | fixed_ips                   | -1    |
  | metadata_items              | 128   |
  | injected_files              | 5     |
  | injected_file_content_bytes | 10240 |
  | injected_file_path_bytes    | 255   |
  | key_pairs                   | 100   |
  | security_groups             | 10    |
  | security_group_rules        | 20    |
  +-----------------------------+-------+

  then i delete the user called test2

  [root@njq002 ~(keystone_admin)]# keystone  user-delete  be4fb020ae8b4001afb1797d81a3d903
  [root@njq002 ~(keystone_admin)]# keystone user-list --tenant bug_test
  +----------------------------------+-------+---------+-------+
  |                id                |  name | enabled | email |
  +----------------------------------+-------+---------+-------+
  | 91c422e673ad4c399aace18ba5c4f049 | test1 |   True  |       |
  +----------------------------------+-------+---------+-------+

  Finally, I execute
  “nova quota-show  --tenant  c93d944ee63a45e0880161608e62eb83 --user be4fb020ae8b4001afb1797d81a3d903”

  Expected result:

  I think the system should be prompt something like：The user does not
  exist

  but the actual result:
  [root@njq002 ~(keystone_admin)]# nova quota-show  --tenant  c93d944ee63a45e0880161608e62eb83 --user be4fb020ae8b4001afb1797d81a3d903
  +-----------------------------+-------+
  | Quota                       | Limit |
  +-----------------------------+-------+
  | instances                   | 8     |
  | cores                       | 20    |
  | ram                         | 51200 |
  | floating_ips                | 10    |
  | fixed_ips                   | -1    |
  | metadata_items              | 128   |
  | injected_files              | 5     |
  | injected_file_content_bytes | 10240 |
  | injected_file_path_bytes    | 255   |
  | key_pairs                   | 100   |
  | security_groups             | 10    |
  | security_group_rules        | 20    |
  +-----------------------------+-------+

  I don't think this is very reasonable

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