yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #29288
[Bug 1431201] [NEW] kilo controller cann't conduct juno compute nodes
Public bug reported:
When I tried to use kilo controller to conduct juno compute nodes, the
juno nova-compute service start with the following two errors:
1. 2015-03-10 06:37:18.525 18900 TRACE nova.openstack.common.threadgroup return self._update_available_resource(context, resources)
2015-03-10 06:37:18.525 18900 TRACE nova.openstack.common.threadgroup File "/usr/lib/python2.6/site-packages/nova/openstack/common/lockutils.py", line 272, in inner
2015-03-10 06:37:18.525 18900 TRACE nova.openstack.common.threadgroup return f(*args, **kwargs)
2015-03-10 06:37:18.525 18900 TRACE nova.openstack.common.threadgroup File "/usr/lib64/python2.6/contextlib.py", line 34, in __exit__
2015-03-10 06:37:18.525 18900 TRACE nova.openstack.common.threadgroup self.gen.throw(type, value, traceback)
2015-03-10 06:37:18.525 18900 TRACE nova.openstack.common.threadgroup File "/usr/lib/python2.6/site-packages/nova/openstack/common/lockutils.py", line 236, in lock
2015-03-10 06:37:18.525 18900 TRACE nova.openstack.common.threadgroup yield int_lock
2015-03-10 06:37:18.525 18900 TRACE nova.openstack.common.threadgroup File "/usr/lib/python2.6/site-packages/nova/openstack/common/lockutils.py", line 272, in inner
2015-03-10 06:37:18.525 18900 TRACE nova.openstack.common.threadgroup return f(*args, **kwargs)
2015-03-10 06:37:18.525 18900 TRACE nova.openstack.common.threadgroup File "/usr/lib/python2.6/site-packages/nova/compute/resource_tracker.py", line 377, in _update_available_resource
2015-03-10 06:37:18.525 18900 TRACE nova.openstack.common.threadgroup self._sync_compute_node(context, resources)
2015-03-10 06:37:18.525 18900 TRACE nova.openstack.common.threadgroup File "/usr/lib/python2.6/site-packages/nova/compute/resource_tracker.py", line 388, in _sync_compute_node
2015-03-10 06:37:18.525 18900 TRACE nova.openstack.common.threadgroup compute_node_refs = service['compute_node']
2015-03-10 06:37:18.525 18900 TRACE nova.openstack.common.threadgroup KeyError: 'compute_node'
We can revert this commit to fix this error:
https://github.com/openstack/nova/commit/83b64ceb871b1553b1bb1e0bb9270816db892552
2. 2015-03-10 06:41:29.388 19336 TRACE nova.virt.libvirt.driver File "/usr/lib/python2.6/site-packages/nova/rpc.py", line 111, in deserialize_entity
2015-03-10 06:41:29.388 19336 TRACE nova.virt.libvirt.driver return self._base.deserialize_entity(context, entity)
2015-03-10 06:41:29.388 19336 TRACE nova.virt.libvirt.driver File "/usr/lib/python2.6/site-packages/nova/objects/base.py", line 649, in deserialize_entity
2015-03-10 06:41:29.388 19336 TRACE nova.virt.libvirt.driver entity = self._process_object(context, entity)
2015-03-10 06:41:29.388 19336 TRACE nova.virt.libvirt.driver File "/usr/lib/python2.6/site-packages/nova/objects/base.py", line 615, in _process_object
2015-03-10 06:41:29.388 19336 TRACE nova.virt.libvirt.driver e.kwargs['supported'])
2015-03-10 06:41:29.388 19336 TRACE nova.virt.libvirt.driver File "/usr/lib/python2.6/site-packages/nova/conductor/api.py", line 217, in object_backport
2015-03-10 06:41:29.388 19336 TRACE nova.virt.libvirt.driver return self._manager.object_backport(context, objinst, target_version)
2015-03-10 06:41:29.388 19336 TRACE nova.virt.libvirt.driver File "/usr/lib/python2.6/site-packages/nova/conductor/rpcapi.py", line 358, in object_backport
2015-03-10 06:41:29.388 19336 TRACE nova.virt.libvirt.driver target_version=target_version)
2015-03-10 06:41:29.388 19336 TRACE nova.virt.libvirt.driver File "/usr/lib/python2.6/site-packages/oslo/messaging/rpc/client.py", line 152, in call
We can revert this commit to fix this error:
https://github.com/openstack/nova/commit/f287b75138129542436b2085d52d6fe201ca7e14
Andbody know is there something like gate keeper to make kilo controller can keep conducting the juno compute nodes ? Thanks!
** 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/1431201
Title:
kilo controller cann't conduct juno compute nodes
Status in OpenStack Compute (Nova):
New
Bug description:
When I tried to use kilo controller to conduct juno compute nodes,
the juno nova-compute service start with the following two errors:
1. 2015-03-10 06:37:18.525 18900 TRACE nova.openstack.common.threadgroup return self._update_available_resource(context, resources)
2015-03-10 06:37:18.525 18900 TRACE nova.openstack.common.threadgroup File "/usr/lib/python2.6/site-packages/nova/openstack/common/lockutils.py", line 272, in inner
2015-03-10 06:37:18.525 18900 TRACE nova.openstack.common.threadgroup return f(*args, **kwargs)
2015-03-10 06:37:18.525 18900 TRACE nova.openstack.common.threadgroup File "/usr/lib64/python2.6/contextlib.py", line 34, in __exit__
2015-03-10 06:37:18.525 18900 TRACE nova.openstack.common.threadgroup self.gen.throw(type, value, traceback)
2015-03-10 06:37:18.525 18900 TRACE nova.openstack.common.threadgroup File "/usr/lib/python2.6/site-packages/nova/openstack/common/lockutils.py", line 236, in lock
2015-03-10 06:37:18.525 18900 TRACE nova.openstack.common.threadgroup yield int_lock
2015-03-10 06:37:18.525 18900 TRACE nova.openstack.common.threadgroup File "/usr/lib/python2.6/site-packages/nova/openstack/common/lockutils.py", line 272, in inner
2015-03-10 06:37:18.525 18900 TRACE nova.openstack.common.threadgroup return f(*args, **kwargs)
2015-03-10 06:37:18.525 18900 TRACE nova.openstack.common.threadgroup File "/usr/lib/python2.6/site-packages/nova/compute/resource_tracker.py", line 377, in _update_available_resource
2015-03-10 06:37:18.525 18900 TRACE nova.openstack.common.threadgroup self._sync_compute_node(context, resources)
2015-03-10 06:37:18.525 18900 TRACE nova.openstack.common.threadgroup File "/usr/lib/python2.6/site-packages/nova/compute/resource_tracker.py", line 388, in _sync_compute_node
2015-03-10 06:37:18.525 18900 TRACE nova.openstack.common.threadgroup compute_node_refs = service['compute_node']
2015-03-10 06:37:18.525 18900 TRACE nova.openstack.common.threadgroup KeyError: 'compute_node'
We can revert this commit to fix this error:
https://github.com/openstack/nova/commit/83b64ceb871b1553b1bb1e0bb9270816db892552
2. 2015-03-10 06:41:29.388 19336 TRACE nova.virt.libvirt.driver File "/usr/lib/python2.6/site-packages/nova/rpc.py", line 111, in deserialize_entity
2015-03-10 06:41:29.388 19336 TRACE nova.virt.libvirt.driver return self._base.deserialize_entity(context, entity)
2015-03-10 06:41:29.388 19336 TRACE nova.virt.libvirt.driver File "/usr/lib/python2.6/site-packages/nova/objects/base.py", line 649, in deserialize_entity
2015-03-10 06:41:29.388 19336 TRACE nova.virt.libvirt.driver entity = self._process_object(context, entity)
2015-03-10 06:41:29.388 19336 TRACE nova.virt.libvirt.driver File "/usr/lib/python2.6/site-packages/nova/objects/base.py", line 615, in _process_object
2015-03-10 06:41:29.388 19336 TRACE nova.virt.libvirt.driver e.kwargs['supported'])
2015-03-10 06:41:29.388 19336 TRACE nova.virt.libvirt.driver File "/usr/lib/python2.6/site-packages/nova/conductor/api.py", line 217, in object_backport
2015-03-10 06:41:29.388 19336 TRACE nova.virt.libvirt.driver return self._manager.object_backport(context, objinst, target_version)
2015-03-10 06:41:29.388 19336 TRACE nova.virt.libvirt.driver File "/usr/lib/python2.6/site-packages/nova/conductor/rpcapi.py", line 358, in object_backport
2015-03-10 06:41:29.388 19336 TRACE nova.virt.libvirt.driver target_version=target_version)
2015-03-10 06:41:29.388 19336 TRACE nova.virt.libvirt.driver File "/usr/lib/python2.6/site-packages/oslo/messaging/rpc/client.py", line 152, in call
We can revert this commit to fix this error:
https://github.com/openstack/nova/commit/f287b75138129542436b2085d52d6fe201ca7e14
Andbody know is there something like gate keeper to make kilo controller can keep conducting the juno compute nodes ? Thanks!
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1431201/+subscriptions
Follow ups
References