yahoo-eng-team team mailing list archive

[Phil Day <1190360@xxxxxxxxxxxxxxxxxx>]

Agree this is covered by that fix - I think it was a problem in
stacktach that made me think it wasn't

** Changed in: nova
       Status: Incomplete => Invalid

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

Title:
  Deleting an instance in the API layer does not send usage
  notifications

Status in OpenStack Compute (Nova):
  Invalid

Bug description:
  If the compute API layer decides to delete an instance itself rather
  than send the request to the compute host, for example because there
  is no host (not yet scheduled) or the host is down then the
  compute.delete.start and compute.delete.end notification messages are
  not send - which can be confusing for Billing and monitoring systems
  listening on the notification queue.

  Currently only an update message for the task state being set to
  "Deleting"  is generated.

  Although the API can't generate the usage data that the compute host
  would include it could at least send delete.start and delete.end
  messages.

  It could also, or maybe instead, set the vm_state to DELETED and
  generate the update event for that.

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