yahoo-eng-team team mailing list archive

[melanie witt <1410032@xxxxxxxxxxxxxxxxxx>]

This bug is over 2 years old and has to do with reservations/usage being
reset to 0 when a quota limit is deleted. Quotas were re-architected in
Pike to not track reservations/usage separately and instead count usage
of resources directly, so this problem should not exist in Pike and
onward.

We aren't going to fix the legacy code, so marking this as "Won't Fix".

** Changed in: nova
       Status: Confirmed => Won't Fix

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

Title:
   Incorrect Nova quota usage shown via CLI/API after Quota Settings
  Changed

Status in OpenStack Compute (nova):
  Won't Fix

Bug description:
  Reproduce steps:
  1.Update nova quota settings.
     nova quota-update --ram 40960 tenant_ID
     nova quota-update --instance 50 tenant_ID
  2.Delete the quota settings and the quota should back to the default.
    nova quota-delete --tenant TENANT_ID
    nova quota-SHOW --tenant TENANT_ID
  3.Query nova quota usage
    nova absolute-limits --tenant TENANT_ID
    nova usage show "0", it is not correct.

  The issue is observed on Havana & icehouse.

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