← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1653862] [NEW] hyper-v: Exception dispatching event <LifecycleEvent: 1483485307.93, 9279c28b-b957-4743-8727-81716783a86b => Stopped>: <x_wmi: Not found >

 

Public bug reported:

I see these errors quite a bit in the n-cpu logs for hyperv CI runs:

2017-01-03 23:15:08.141 10848 80822320 MainThread ERROR nova.virt.driver
[req-050d06ec-3636-4a5d-8b73-0531ef62055a - - - - -] Exception
dispatching event <LifecycleEvent: 1483485307.93,
9279c28b-b957-4743-8727-81716783a86b => Stopped>: <x_wmi: Not found  >

http://64.119.130.115/nova/140045/51/Hyper-V_logs/c2-r22-u04-n03/nova-
compute.log.gz

I assume this is a lifecycle event for an instance that has been
deleted. We're logging an error because of a problem dispatching the
event.

I'm not totally sure how to handle this, but if the virt driver could
raise a NotFound or something we could handle that and not log it as an
ERROR in the n-cpu logs.

** Affects: nova
     Importance: Low
         Status: Confirmed


** Tags: hyper-v

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

Title:
  hyper-v: Exception dispatching event <LifecycleEvent: 1483485307.93,
  9279c28b-b957-4743-8727-81716783a86b => Stopped>: <x_wmi: Not found  >

Status in OpenStack Compute (nova):
  Confirmed

Bug description:
  I see these errors quite a bit in the n-cpu logs for hyperv CI runs:

  2017-01-03 23:15:08.141 10848 80822320 MainThread ERROR
  nova.virt.driver [req-050d06ec-3636-4a5d-8b73-0531ef62055a - - - - -]
  Exception dispatching event <LifecycleEvent: 1483485307.93,
  9279c28b-b957-4743-8727-81716783a86b => Stopped>: <x_wmi: Not found  >

  http://64.119.130.115/nova/140045/51/Hyper-V_logs/c2-r22-u04-n03/nova-
  compute.log.gz

  I assume this is a lifecycle event for an instance that has been
  deleted. We're logging an error because of a problem dispatching the
  event.

  I'm not totally sure how to handle this, but if the virt driver could
  raise a NotFound or something we could handle that and not log it as
  an ERROR in the n-cpu logs.

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


Follow ups