yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #67151
[Bug 1653862] Re: hyper-v: Exception dispatching event <LifecycleEvent: 1483485307.93, 9279c28b-b957-4743-8727-81716783a86b => Stopped>: <x_wmi: Not found >
This has been fixed at the os-win level, which is now raising a
HyperVVMNotFoundException exception that can properly be handled by the
Nova Hyper-V driver.
Note that a debug message will still be logged in this situation [1], as
seen on a recent Hyper-V CI run[2].
[1] 2017-08-31 12:26:16.625 2336 90871568 MainThread DEBUG os_win._utils [req-69dcf4f7-c61f-4fd0-b7fc-c8adb1026821 - - - - -] x_wmi: Not Found exception raised while running get_vm_summary_info inner C:\Python27\lib\site-packages\os_win\_utils.py:244
[2] http://cloudbase-ci.com/nova/499690/2/Hyper-V_logs/192.168.5.111-compute01/nova-compute.log.gz
FWIW, the CI hardware is being moved, for which reason old CI result
URLs may be unavailable.
** Changed in: nova
Status: Confirmed => 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/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):
Fix Released
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
References