ERR: Exception dispatching event <nova.virt.event.LifecycleEvent object at 0x3e49cd0>

Bug #1356257 reported by Anastasia Palkina
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Mirantis OpenStack
Fix Released
Low
Unassigned
5.0.x
Fix Released
Low
Unassigned
5.1.x
Fix Released
Low
Unassigned
6.0.x
Fix Released
Low
Unassigned

Bug Description

"build_id": "2014-08-11_12-45-06",
"mirantis": "yes",
"build_number": "169",
"ostf_sha": "09b6bccf7d476771ac859bb3c76c9ebec9da9e1f",
"nailgun_sha": "04ada3cd7ef14f6741a05fd5d6690260f9198095",
"production": "docker",
"api": "1.0",
"fuelmain_sha": "43374c706b4fdce28aeb4ef11e69a53f41646740",
"astute_sha": "6db5f5031b74e67b92fcac1f7998eaa296d68025",
"release": "5.0.1",
"fuellib_sha": "a31dbac8fff9cf6bc4cd0d23459670e34b27a9ab"

1. Create new environment (CentOS, HA mode)
2. Choose nova-network, flat
3. Add 3 controllers, 1 compute, 1 compute+cinder
4. Start deployment. It was seccessful
5. There are errors on compute nodes (node-4,5) in nova-compute.log:

2014-08-13 08:40:14 ERROR

nova.virt.driver [-] Exception dispatching event <nova.virt.event.LifecycleEvent object at 0x2c82110>: Info cache for instance cb0c2e45-8912-490e-9f2c-fa88cf94b633 could not be found.
2014-08-13T08:40:14.363250+00:00 debug: Traceback (most recent call last):
2014-08-13T08:40:14.363250+00:00 debug: File "/usr/lib/python2.6/site-packages/nova/conductor/manager.py", line 597, in _object_dispatch
2014-08-13T08:40:14.363250+00:00 debug: return getattr(target, method)(context, *args, **kwargs)
2014-08-13T08:40:14.363250+00:00 debug: File "/usr/lib/python2.6/site-packages/nova/objects/base.py", line 151, in wrapper
2014-08-13T08:40:14.363250+00:00 debug: return fn(self, ctxt, *args, **kwargs)
2014-08-13T08:40:14.363250+00:00 debug: File "/usr/lib/python2.6/site-packages/nova/objects/instance.py", line 500, in refresh
2014-08-13T08:40:14.363250+00:00 debug: self.info_cache.refresh()
2014-08-13T08:40:14.363250+00:00 debug: File "/usr/lib/python2.6/site-packages/nova/objects/base.py", line 151, in wrapper
2014-08-13T08:40:14.363250+00:00 debug: return fn(self, ctxt, *args, **kwargs)
2014-08-13T08:40:14.363250+00:00 debug: File "/usr/lib/python2.6/site-packages/nova/objects/instance_info_cache.py", line 103, in refresh
2014-08-13T08:40:14.363250+00:00 debug: self.instance_uuid)
2014-08-13T08:40:14.363250+00:00 debug: File "/usr/lib/python2.6/site-packages/nova/objects/base.py", line 112, in wrapper
2014-08-13T08:40:14.363250+00:00 debug: result = fn(cls, context, *args, **kwargs)
2014-08-13T08:40:14.363250+00:00 debug: File "/usr/lib/python2.6/site-packages/nova/objects/instance_info_cache.py", line 70, in get_by_instance_uuid
2014-08-13T08:40:14.365746+00:00 debug: instance_uuid=instance_uuid)
2014-08-13T08:40:14.365746+00:00 debug: InstanceInfoCacheNotFound: Info cache for instance cb0c2e45-8912-490e-9f2c-fa88cf94b633 could not be found.

Also I found similar bug with "Review in progress" status in gerrit:
https://bugs.launchpad.net/nova/+bug/1304968

Logs are here: https://drive.google.com/a/mirantis.com/file/d/0B6SjzarTGFxabEI1Wm11b0c0Y2M/edit?usp=sharing

Tags: nova
affects: fuel → mos
Changed in mos:
milestone: 5.0.2 → none
status: New → Triaged
tags: added: nova
Changed in mos:
assignee: MOS Nova (mos-nova) → Mikhail Durnosvistov (mdurnosvistov)
status: Triaged → In Progress
milestone: none → 5.1
Revision history for this message
Roman Podoliaka (rpodolyaka) wrote :

This happens once per instance deletion and does not affect any other instances (or the new ones). At the same time, log files are littered with misleading tracebacks.

Revision history for this message
Dmitry Mescheryakov (dmitrymex) wrote :

Moving to 6.0 since we've already reached soft code freeze and it is a minor issue

no longer affects: mos/5.1.x
no longer affects: mos/6.0.x
Revision history for this message
Dmitry Borodaenko (angdraug) wrote :

Why is this targeted for maintenance releases if it's a Low priority bug?

Revision history for this message
Roman Podoliaka (rpodolyaka) wrote :
Revision history for this message
Roman Podoliaka (rpodolyaka) wrote :

The fix is in the latest ISOs

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.