nova shows wrong RAM usage

Bug #1692491 reported by int32bit
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
New
Undecided
int32bit

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

Revision history for this message
int32bit (int32bit) wrote :

Obviously, we can't get hw_video from flavor, because the flavor will be changed by user. I think we need add hw_video:ram_max_mb to the server metadata, and read this value when delete server. Or we just ignore hw_video when create a new sever.

Changed in nova:
assignee: nobody → int32bit (int32bit)
Revision history for this message
Matt Riedemann (mriedem) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.