yahoo-eng-team team mailing list archive

[Chris Behrens <1296414@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

There are a couple of cases in the compute manager where we don't pass
reservations to _delete_instance().  For example, one of them is
cleaning up when we see a delete that is stuck in DELETING.

The only place we ever update quotas as part of delete should be when
the instance DB record is removed. If something is stuck in DELETING, it
means that the quota was not updated.  We should make sure we're always
updating the quota when the instance DB record is removed.

(Soft delete kinda throws a wrench in this, hrmph, because I think you
want soft deleted instances to not count against quotas -- yet their DB
records will still exist.)

** Affects: nova
     Importance: Undecided
         Status: New

** Description changed:

  There are a couple of cases in the compute manager where we don't pass
  reservations to _delete_instance().  For example, one of them is
  cleaning up when we see a delete that is stuck in DELETING.
  
  The only place we ever update quotas as part of delete should be when
  the instance DB record is removed. If something is stuck in DELETING, it
  means that the quota was not updated.  We should make sure we're always
  updating the quota when the instance DB record is removed.
+ 
+ (Soft delete kinda throws a wrench in this, hrmph, because I think you
+ want soft deleted instances to not count against quotas -- yet their DB
+ records will still exist.)

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

Title:
  quotas not updated when periodic tasks or startup finish deletes

Status in OpenStack Compute (Nova):
  New

Bug description:
  There are a couple of cases in the compute manager where we don't pass
  reservations to _delete_instance().  For example, one of them is
  cleaning up when we see a delete that is stuck in DELETING.

  The only place we ever update quotas as part of delete should be when
  the instance DB record is removed. If something is stuck in DELETING,
  it means that the quota was not updated.  We should make sure we're
  always updating the quota when the instance DB record is removed.

  (Soft delete kinda throws a wrench in this, hrmph, because I think you
  want soft deleted instances to not count against quotas -- yet their
  DB records will still exist.)

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