yahoo-eng-team team mailing list archive

[Mark McLoughlin <markmc@xxxxxxxxxx>]

** Changed in: horizon/folsom
       Status: Fix Committed => Fix Released

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

Title:
  Quota tally not handling unlimited values correctly

Status in OpenStack Dashboard (Horizon):
  Fix Released
Status in OpenStack Dashboard (Horizon) folsom series:
  Fix Released

Bug description:
  Horizon seems to be interpreting "-1" (unlimited) quotas literally
  when tallying quotas, setting the 'available' field to 0 instead of
  infinity (probably because the expectation used to be that an
  unlimited quota would always be returned as None).

  https://github.com/openstack/horizon/blob/master/openstack_dashboard/usage/quotas.py#L30
  -- also checking for -1 when tallying unlimited quotas solves the
  problem.

  The problem becomes more obvious in the context of ux improvements
  based on quotas such as
  https://bugs.launchpad.net/horizon/+bug/1033829, but it's also
  possible to check it by doing "nova quota-update --ram -1
  <project_id>" then visit the project overview page: it will read "Used
  X MB of -1 MB Available RAM". It should be "Used X MB of inf MB
  Available RAM" -- although it would also be nice to display a nicer
  message when there are no limit!

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