yahoo-eng-team team mailing list archive

[int32bit <krystism@xxxxxxxxx>]

Public bug reported:

If flavor has hw_video:ram_max_mb value, nova will add this value to the
project usage[1]. But when we delete this server, it seems we don't
cover this case. So we will always get wrong ram usage.

For example, we create a server with flavor f, whose ram is 1024 and
hw_video:ram_max_mb is 64, then we will compute quota usage as 1024 +
64, but when we delete this server, we only release 1024, rather than
1024 + 64. As a result, the usage may incremente constantly， until over
max limit.

[1]
https://github.com/openstack/nova/blob/master/nova/compute/api.py#L352-L353

** Affects: nova
     Importance: Undecided
     Assignee: int32bit (int32bit)
         Status: New

** Changed in: nova
     Assignee: (unassigned) => int32bit (int32bit)

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

Title:
  nova shows wrong RAM usage

Status in OpenStack Compute (nova):
  New

Bug description:
  If flavor has hw_video:ram_max_mb value, nova will add this value to
  the project usage[1]. But when we delete this server, it seems we
  don't cover this case. So we will always get wrong ram usage.

  For example, we create a server with flavor f, whose ram is 1024 and
  hw_video:ram_max_mb is 64, then we will compute quota usage as 1024 +
  64, but when we delete this server, we only release 1024, rather than
  1024 + 64. As a result, the usage may incremente constantly， until
  over max limit.

  [1]
  https://github.com/openstack/nova/blob/master/nova/compute/api.py#L352-L353

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