yahoo-eng-team team mailing list archive

[OpenStack Infra <1681989@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/456050
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f2d03bf92db3615693b62f4f3274b867f00c0967
Submitter: Jenkins
Branch:    master

commit f2d03bf92db3615693b62f4f3274b867f00c0967
Author: falseuser <zhaomingjun@xxxxxxxxxxxxxxx>
Date:   Wed Apr 12 03:35:33 2017 +0000

    [BugFix] Release the memory quota for video ram when deleting an instance.
    
    When creating an instance, the quota is used to contain vram,
    and the deletion of the instance does not release the memory quota for vram,
    if delete intance it need to release the memory quota for vram.
    
    Change-Id: Iee2925c585c87d9885fd4bfe38cd9b4d316f5dab
    Closes-Bug: #1681989


** Changed in: nova
       Status: In Progress => Fix Released

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

Title:
  the deletion of the instance does not release the memory quota for
  vram

Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Compute (nova) ocata series:
  New

Bug description:
  When creating an instance, the quota is used to contain vram, and the
  deletion of the instance does not release the memory quota for vram

  If a flavor defines 512MB of RAM and 64MB of video RAM, creating an instance will take up 576MB of memory quota, but after deleting the instance, it will only release 512MB of memory quotas.
  In this way, after multiple creation and deletion of the virtual machine, it will gradually run out of the memory quota, but in fact did not run so many instances.

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