yahoo-eng-team team mailing list archive

[Matthew Booth <mbooth@xxxxxxxxxx>]

Public bug reported:

If the compute api service does a 'local delete', it only emits legacy
notifications when the operation starts and ends. If the delete goes to
a compute host, the compute host emits both legacy and versioned
notifications. This is both inconsistent, and a gap in versioned
notifications.

It would appear that every caller of
compute_utils.notify_about_instance_delete in compute.API fails to emit
versioned notifications. I suggest that the best way to fix this will be
to fix compute_utils.notify_about_instance_delete, but note that there's
also a caller in compute.Manager which emits versioned notifications
explicitly.

** Affects: nova
     Importance: Undecided
         Status: New

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

Title:
  Local delete emits only legacy start and end notifications

Status in OpenStack Compute (nova):
  New

Bug description:
  If the compute api service does a 'local delete', it only emits legacy
  notifications when the operation starts and ends. If the delete goes
  to a compute host, the compute host emits both legacy and versioned
  notifications. This is both inconsistent, and a gap in versioned
  notifications.

  It would appear that every caller of
  compute_utils.notify_about_instance_delete in compute.API fails to
  emit versioned notifications. I suggest that the best way to fix this
  will be to fix compute_utils.notify_about_instance_delete, but note
  that there's also a caller in compute.Manager which emits versioned
  notifications explicitly.

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