yahoo-eng-team team mailing list archive

[Matt Riedemann <mriedem.os@xxxxxxxxx>]

*** This bug is a duplicate of bug 1670627 ***
    https://bugs.launchpad.net/bugs/1670627

For master (pike) this is the fix:

https://review.openstack.org/#/c/443403/

For ocata, the fix will be a backport of this:

https://review.openstack.org/#/c/443395/

** This bug has been marked a duplicate of bug 1670627
   quota is always in-use after delete the ERROR instances

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

Title:
  Nova fails to correctly update the quota when deleting lots of VMs,
  some of which previously failed due to a quota error

Status in OpenStack Compute (nova):
  In Progress

Bug description:
  When VMs goes to ERROR state after the block device mapping nova updates the quota for adding the instance/CPU/RAM to the quota
  but when we delete those VMs nova forgets the release/update the CPU/RAM/Instance quota 

  Steps to reproduce:
  1. Set the quota limit for volumes to 10 and VMs to 50
  2. create 20 VMs by using option boot from volume from horizon
  Observation:
  10 VMs comes to active state and 10 goes to ERROR state (As expected)

  3. delete all VMs

  Expectation: CPU/RAM/Instance used quota will come to "0"
  Actual: CPU/RAM/Instance quota is not coming to "0" 
  CPU used quota shows 10 (As the VM is created from M1.SMALL flavor)
  Instance quota shows 10
  RAM quota shows 20480MB

  which is quite unexpected

  Its seems it is a blocker for Ocata release

  I am running from the stable/Ocata

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