Re: [Rdo-list] VM instance will not start

On your controller node, do you have RabbitMQ running? # systemctl status rabbitmq-server I suspect that this isn’t running, yet the firewall port is open, hence the connection refused message. Cheers Rhys > On 22 Jul 2015, at 23:23, brian lee <brian(a)brianlee.org&gt; wrote: > > The compute node can ping the controller. > > I did just find this error in the compute log file: > > 2015-07-22 21:30:36.756 18880 ERROR nova.compute.manager [-] Instance failed network setup after 1 attempt(s) > 2015-07-22 21:30:36.756 18880 TRACE nova.compute.manager Traceback (most recent call last): > 2015-07-22 21:30:36.756 18880 TRACE nova.compute.manager File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 1770, in _allocate_network_async > 2015-07-22 21:30:36.756 18880 TRACE nova.compute.manager dhcp_options=dhcp_options) > 2015-07-22 21:30:36.756 18880 TRACE nova.compute.manager File "/usr/lib/python2.7/site-packages/nova/network/api.py", line 49, in wrapped > 2015-07-22 21:30:36.756 18880 TRACE nova.compute.manager return func(self, context, *args, **kwargs) > 2015-07-22 21:30:36.756 18880 TRACE nova.compute.manager File "/usr/lib/python2.7/site-packages/nova/network/base_api.py", line 64, in wrapper > 2015-07-22 21:30:36.756 18880 TRACE nova.compute.manager res = f(self, context, *args, **kwargs) > 2015-07-22 21:30:36.756 18880 TRACE nova.compute.manager File "/usr/lib/python2.7/site-packages/nova/network/api.py", line 281, in allocate_for_instance > 2015-07-22 21:30:36.756 18880 TRACE nova.compute.manager nw_info = self.network_rpcapi.allocate_for_instance(context, **args) > 2015-07-22 21:30:36.756 18880 TRACE nova.compute.manager File "/usr/lib/python2.7/site-packages/nova/network/rpcapi.py", line 152, in allocate_for_instance > 2015-07-22 21:30:36.756 18880 TRACE nova.compute.manager macs=jsonutils.to_primitive(macs)) > 2015-07-22 21:30:36.756 18880 TRACE nova.compute.manager File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/client.py", line 156, in call > 2015-07-22 21:30:36.756 18880 TRACE nova.compute.manager retry=self.retry) > 2015-07-22 21:30:36.756 18880 TRACE nova.compute.manager File "/usr/lib/python2.7/site-packages/oslo_messaging/transport.py", line 90, in _send > 2015-07-22 21:30:36.756 18880 TRACE nova.compute.manager timeout=timeout, retry=retry) > 2015-07-22 21:30:36.756 18880 TRACE nova.compute.manager File "/usr/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriver.py", line 350, in send > 2015-07-22 21:30:36.756 18880 TRACE nova.compute.manager retry=retry) > 2015-07-22 21:30:36.756 18880 TRACE nova.compute.manager File "/usr/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriver.py", line 339, in _send > 2015-07-22 21:30:36.756 18880 TRACE nova.compute.manager result = self._waiter.wait(msg_id, timeout) > 2015-07-22 21:30:36.756 18880 TRACE nova.compute.manager File "/usr/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriver.py", line 243, in wait > 2015-07-22 21:30:36.756 18880 TRACE nova.compute.manager message = self.waiters.get(msg_id, timeout=timeout) > 2015-07-22 21:30:36.756 18880 TRACE nova.compute.manager File "/usr/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriver.py", line 149, in get > 2015-07-22 21:30:36.756 18880 TRACE nova.compute.manager 'to message ID %s' % msg_id) > 2015-07-22 21:30:36.756 18880 TRACE nova.compute.manager MessagingTimeout: Timed out waiting for a reply to message ID 63bcf088157e44b592913f7245249d07 > 2015-07-22 21:30:36.756 18880 TRACE nova.compute.manager > 2015-07-22 21:30:36.761 18880 ERROR nova.compute.manager [req-3c3ddcae-0f6a-4aed-9f72-2ec3fd8ac073 - - - - -] [instance: 5e4d609c-0139-44cd-94e3-ecb765209b1e] Instance failed to spawn > > > --Brian > > On Wed, Jul 22, 2015 at 5:20 PM, Kevin Tibi <kevintibi(a)hotmail.com&gt; wrote: > Hi, > > I see error for rabbitmq. The compute node can ping the controller ? > > Kevin Tibi > > Le 23 juil. 2015 00:07, "brian lee" <brian(a)brianlee.org&gt; a écrit : > I have a fresh 2 node install of Kilo, maybe working with Nova networking (I dont know yet). When I try to start a VM I get this error in Horizon: > Error: No valid host was found. There are not enough hosts available. > > There is nothing really telling in the logs beside this in the scheduler: > > 2015-07-22 19:57:56.232 22843 ERROR oslo_messaging._drivers.impl_rabbit [-] Failed to consume message from queue: > 2015-07-22 19:59:19.465 997 WARNING oslo_config.cfg [req-d19b6788-9f3b-49e6-9124-b945f4c3e3e6 - - - - -] Option "sql_connection" from group "DEFAULT" is deprecated. Use option "connection" from group "database". > 2015-07-22 19:59:20.739 997 WARNING oslo_config.cfg [req-d19b6788-9f3b-49e6-9124-b945f4c3e3e6 - - - - -] Option "lock_path" from group "DEFAULT" is deprecated. Use option "lock_path" from group "oslo_concurrency". > 2015-07-22 19:59:20.785 997 INFO nova.service [-] Starting scheduler node (version 2015.1.0-3.el7) > 2015-07-22 19:59:20.959 997 INFO oslo_messaging._drivers.impl_rabbit [req-0d6a61c6-54eb-42df-a2a2-596d535a8ac5 - - - - -] Connecting to AMQP server on 10.32.97.133:5672 > 2015-07-22 19:59:20.976 997 ERROR oslo_messaging._drivers.impl_rabbit [req-0d6a61c6-54eb-42df-a2a2-596d535a8ac5 - - - - -] AMQP server on 10.32.97.133:5672 is unreachable: [Errno 111] ECONNREFUSED. Trying again in 1 seconds. > > I am not seeing any other errors in the log files, any idea what else to check? > > --Brian > > > _______________________________________________ > Rdo-list mailing list > Rdo-list(a)redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > > To unsubscribe: rdo-list-unsubscribe(a)redhat.com > > _______________________________________________ > Rdo-list mailing list > Rdo-list(a)redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > > To unsubscribe: rdo-list-unsubscribe(a)redhat.com