yahoo-eng-team team mailing list archive

[Maithem <1250320@xxxxxxxxxxxxxxxxxx>]

This is not a bug, the reason you are able to set ram to zero is because
the tenant total used ram is 0. Basically when you update an attribute
(i.e. ram) , your lower bound becomes min(0, used so far). So for
example, if you have one instance running and it is assigned 100mb, then
when try to update the ram to 0 it will throw an exception.

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

** Changed in: nova
     Assignee: Maithem (maithem) => (unassigned)

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

Title:
  There is not any error information while try to update RAM of quota
  with 0

Status in OpenStack Compute (Nova):
  Invalid

Bug description:
  [root@ns11 ~]# nova quota-update --ram 0   a1a8dbd9285f4d0ab61d13af3958c8c9
  [root@ns11 ~]# nova quota-show --tenant a1a8dbd9285f4d0ab61d13af3958c8c9
  +-----------------------------+-------+
  | Quota                       | Limit |
  +-----------------------------+-------+
  | instances                   | 10    |
  | cores                       | 20    |
  | ram                         | 0    |
  | floating_ips                | 10    |
  | fixed_ips                   | -1    |
  | metadata_items              | 128   |
  | injected_files              | 1     |
  | injected_file_content_bytes | 10240 |
  | injected_file_path_bytes    | 255   |
  | key_pairs                   | 100   |
  | security_groups             | 10    |
  | security_group_rules        | 20    |
  +-----------------------------+-------+

  # EXPECTED RESULTS 
  Prompt the input RAM in quota should be greater than 0

  # Actual Result
  update is successful

   it doesn't make sense to set the quota for RAM, DISK, CPU with 0. It
  is impossible for a virtual machine without RAM or DISK or CPU.  so
  when the user tries to set RAM with 0, it is better to prompt error
  information and suggest to set with a configured default value, it
  will be better user experience.

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