yahoo-eng-team team mailing list archive

[Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>]

** Changed in: nova
       Status: Fix Committed => 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/1250206

Title:
  Local delete emits delete.end notification without delete_at

Status in OpenStack Compute (Nova):
  Fix Released

Bug description:
  In cases where Nova falls back to doing a local delete at the API
  (compute host down), it is possible for the delete.end notification to
  get emitted without deleted_at being set.

  Steps to reproduce (with notifications enabled):
  1) Create instance and wait for it to go active
  2) Take compute host for the instance down
  3) Delete instance
  4) Observe compute.instance.delete.end notification with a blank deleted_at

  This seems to be happening because the Instance.destroy() function
  does not update the instance with the latest state from the database
  after calling db.instance_destroy. It is important that the instance
  is updated with the data from the database as the driver automatically
  sets the deleted_at value.

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