fuel-dev team mailing list archive

[Dmitry Ukov <dukov@xxxxxxxxxxxx>]

Hello folks,
I'm observing the following issue with communication between nova-compute
and nova-conductor
 Traceback (most recent call last):
   File "/usr/lib/python2.6/site-packages/nova/servicegroup/drivers/db.py",
line 96, in _report_state
     service.service_ref, state_catalog)
   File "/usr/lib/python2.6/site-packages/nova/conductor/api.py", line 269,
in service_update
     return self._manager.service_update(context, service, values)
   File "/usr/lib/python2.6/site-packages/nova/conductor/rpcapi.py", line
397, in service_update
     service=service_p, values=values)
   File "/usr/lib/python2.6/site-packages/nova/rpcclient.py", line 85, in
call
     return self._invoke(self.proxy.call, ctxt, method, **kwargs)
   File "/usr/lib/python2.6/site-packages/nova/rpcclient.py", line 63, in
_invoke
     return cast_or_call(ctxt, msg, **self.kwargs)
   File
"/usr/lib/python2.6/site-packages/nova/openstack/common/rpc/proxy.py", line
130, in call
     exc.info, real_topic, msg.get('method'))
 Timeout: Timeout while waiting on RPC response - topic: "conductor", RPC
method: "service_update" info: "<unknown>"

After that nova-compute became unavailable nova-conductor and RabbitMQ
services look fine
I'm using Havana release. Any ideas on that issue? Is it possible that it's
connected with VIP migration and rabbit issue?
Thanks in advance.

-- 
Kind regards
Dmitry Ukov
IT Engineer
Mirantis, Inc.