Ask Your Question
1

Juno MessagingTimeout launching an instance

asked 2014-11-18 09:00:33 -0500

azriel gravatar image

Hi, I'm running Ubuntu 14.10 with fresh Juno installation (manual installation) and i'm not able to spin new instances. I'm keep getting this error on nova-conductor.log

2014-11-18 16:46:58.827 4829 ERROR nova.scheduler.driver [req-41e94c9e-423d-4b88-acce-fc18ee9bad6f None] Exception during scheduler.run_instance
2014-11-18 16:46:58.827 4829 TRACE nova.scheduler.driver Traceback (most recent call last):
2014-11-18 16:46:58.827 4829 TRACE nova.scheduler.driver   File "/usr/lib/python2.7/dist-packages/nova/conductor/manager.py", line 614, in build_instances
2014-11-18 16:46:58.827 4829 TRACE nova.scheduler.driver     request_spec, filter_properties)
2014-11-18 16:46:58.827 4829 TRACE nova.scheduler.driver   File "/usr/lib/python2.7/dist-packages/nova/scheduler/client/__init__.py", line 49, in select_destinations
2014-11-18 16:46:58.827 4829 TRACE nova.scheduler.driver     context, request_spec, filter_properties)
2014-11-18 16:46:58.827 4829 TRACE nova.scheduler.driver   File "/usr/lib/python2.7/dist-packages/nova/scheduler/client/__init__.py", line 35, in __run_method
2014-11-18 16:46:58.827 4829 TRACE nova.scheduler.driver     return getattr(self.instance, __name)(*args, **kwargs)
2014-11-18 16:46:58.827 4829 TRACE nova.scheduler.driver   File "/usr/lib/python2.7/dist-packages/nova/scheduler/client/query.py", line 34, in select_destinations
2014-11-18 16:46:58.827 4829 TRACE nova.scheduler.driver     context, request_spec, filter_properties)
2014-11-18 16:46:58.827 4829 TRACE nova.scheduler.driver   File "/usr/lib/python2.7/dist-packages/nova/scheduler/rpcapi.py", line 108, in select_destinations
2014-11-18 16:46:58.827 4829 TRACE nova.scheduler.driver     request_spec=request_spec, filter_properties=filter_properties)
2014-11-18 16:46:58.827 4829 TRACE nova.scheduler.driver   File "/usr/lib/python2.7/dist-packages/oslo/messaging/rpc/client.py", line 152, in call
2014-11-18 16:46:58.827 4829 TRACE nova.scheduler.driver     retry=self.retry)
2014-11-18 16:46:58.827 4829 TRACE nova.scheduler.driver   File "/usr/lib/python2.7/dist-packages/oslo/messaging/transport.py", line 90, in _send
2014-11-18 16:46:58.827 4829 TRACE nova.scheduler.driver     timeout=timeout, retry=retry)
2014-11-18 16:46:58.827 4829 TRACE nova.scheduler.driver   File "/usr/lib/python2.7/dist-packages/oslo/messaging/_drivers/amqpdriver.py", line 408, in send
2014-11-18 16:46:58.827 4829 TRACE nova.scheduler.driver     retry=retry)
2014-11-18 16:46:58.827 4829 TRACE nova.scheduler.driver   File "/usr/lib/python2.7/dist-packages/oslo/messaging/_drivers/amqpdriver.py", line 397, in _send
2014-11-18 16:46:58.827 4829 TRACE nova.scheduler.driver     result = self._waiter.wait(msg_id, timeout)
2014-11-18 16:46:58.827 4829 TRACE nova.scheduler.driver   File "/usr/lib/python2.7/dist-packages/oslo/messaging/_drivers/amqpdriver.py", line 285, in wait
2014-11-18 16:46:58.827 4829 TRACE nova.scheduler.driver     reply, ending = self._poll_connection(msg_id, timeout)
2014-11-18 16:46:58.827 4829 TRACE nova.scheduler.driver   File "/usr/lib/python2.7/dist-packages/oslo/messaging/_drivers/amqpdriver.py", line 235, in _poll_connection
2014-11-18 16:46:58.827 4829 TRACE nova.scheduler.driver     % msg_id)
2014-11-18 16:46:58.827 4829 TRACE nova.scheduler.driver MessagingTimeout: Timed out waiting for ...
(more)
edit retag flag offensive close merge delete

2 answers

Sort by ยป oldest newest most voted
0

answered 2014-11-19 07:30:00 -0500

azriel gravatar image

I't seems like I was able to resolve the issue - 1. verified that rabbitmq is running correct. 2. verified all OpenStack services configuration are using the correct rabbitmq configuration (glance registry and api were incorrect) 3. commented all qpid configuration from glance registry and api. 4. set the hyper-visor localhost hosts with 'controller'.

edit flag offensive delete link more
0

answered 2015-04-01 07:38:40 -0500

ethode gravatar image

Issue I ran into wasn't that rabbit MQ was down, I had the same error however, on the controller node nova-compute was off, and nova-scheduler wasn't running either... Of course both are needed :) Once I turned those on the timeouts stopped

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

Stats

Asked: 2014-11-18 09:00:33 -0500

Seen: 1,009 times

Last updated: Apr 01 '15