Ask Your Question
0

No valid host was found. There are not enough hosts available.

asked 2017-06-20 10:46:27 -0500

AmitAsh gravatar image

Trying to dispatch an instance with a QCOW2 format image built via nodepool image build - ubuntu 14. I'm using QEMU as hypervisor I'm getting the no valid host found error. The stack i got is:

ter_scheduler.py:75}}nderci-02 nova-conductor[7294]: WARNING nova.scheduler.utils [None req-b463abc7-a826-4fe0-a546-040b8ea1e6b6 demo admin] Failed to compute_task_build_instances: No valid host was found. There are not enough hosts available. Jun 20 18:21:26 vm-cinderci-02 nova-conductor[7294]: Traceback (most recent call last): Jun 20 18:21:26 vm-cinderci-02 nova-conductor[7294]: File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/server.py", line 229, in inner Jun 20 18:21:26 vm-cinderci-02 nova-conductor[7294]: return func(args, *kwargs) Jun 20 18:21:26 vm-cinderci-02 nova-conductor[7294]: File "/opt/stack/nova/nova/scheduler/manager.py", line 98, in select_destinations Jun 20 18:21:26 vm-cinderci-02 nova-conductor[7294]: dests = self.driver.select_destinations(ctxt, spec_obj, instance_uuids) Jun 20 18:21:26 vm-cinderci-02 nova-conductor[7294]: File "/opt/stack/nova/nova/scheduler/filter_scheduler.py", line 78, in select_destinations Jun 20 18:21:26 vm-cinderci-02 nova-conductor[7294]: raise exception.NoValidHost(reason=reason) Jun 20 18:21:26 vm-cinderci-02 nova-conductor[7294]: NoValidHost: No valid host was found. There are not enough hosts available. Jun 20 18:21:26 vm-cinderci-02 nova-conductor[7294]: : NoValidHost_Remote: No valid host was found. There are not enough hosts available. Jun 20 18:21:26 vm-cinderci-02 nova-conductor[7294]: Traceback (most recent call last): Jun 20 18:21:26 vm-cinderci-02 nova-conductor[7294]: File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/server.py", line 229, in inner Jun 20 18:21:26 vm-cinderci-02 nova-conductor[7294]: return func(args, *kwargs) Jun 20 18:21:26 vm-cinderci-02 nova-conductor[7294]: File "/opt/stack/nova/nova/scheduler/manager.py", line 98, in select_destinations Jun 20 18:21:26 vm-cinderci-02 nova-conductor[7294]: dests = self.driver.select_destinations(ctxt, spec_obj, instance_uuids) Jun 20 18:21:26 vm-cinderci-02 nova-conductor[7294]: File "/opt/stack/nova/nova/scheduler/filter_scheduler.py", line 78, in select_destinations Jun 20 18:21:26 vm-cinderci-02 nova-conductor[7294]: raise exception.NoValidHost(reason=reason) Jun 20 18:21:26 vm-cinderci-02 nova-conductor[7294]: NoValidHost: No valid host was found. There are not enough hosts available. Jun 20 18:21:26 vm-cinderci-02 nova-conductor[7294]: WARNING nova.scheduler.utils [None req-b463abc7-a826-4fe0-a546-040b8ea1e6b6 demo admin] [instance: 105a8167-4dd9-450b-8b5a-a14abe90e495] Setting instance to ERROR state.: NoValidHost_Remote: No valid host was found. There are not enough hosts available.ci-02 nova-conductor[7294]: Traceback (most recent call last): Jun 20 18:21:26 vm-cinderci-02 nova-conductor[7294]: File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/server.py", line 229, in inner Jun 20 18:21:26 vm-cinderci-02 nova-conductor[7294]: return func(args, *kwargs) Jun 20 18:21:26 vm-cinderci-02 nova-conductor[7294]: File "/opt/stack/nova/nova/scheduler/manager.py", line 98, in select_destinations Jun 20 18:21:26 vm-cinderci-02 nova-conductor[7294]: dests = self.driver.select_destinations(ctxt, spec_obj, instance_uuids) Jun 20 18:21:26 vm-cinderci-02 nova-conductor[7294]: File "/opt/stack/nova/nova/scheduler/filter_scheduler.py", line 78, in select_destinations Jun 20 18:21:26 vm-cinderci-02 nova-conductor[7294]: raise exception ... (more)

edit retag flag offensive close merge delete

2 answers

Sort by ยป oldest newest most voted
2

answered 2017-06-21 12:25:01 -0500

updated 2017-06-21 12:52:28 -0500

This is a common error when the nova-scheduler can't find any suitable compute node to launch instance.

1) Check the output of 'nova-manage service list'. If 'nova-compute' and 'libvirt-bin' services are working fine, then it should show enabled and status should be :-)

2) If any compute node is available and enabled, check /var/log/nova/nova-compute.log in that node and see if you could find any errors. (see the old logs , as you cant see any logs while launching instance as the the request would be stopped at the scheduler itself)

3) If everything is fine and clean, then the compute node should be lack of resources. In this case, you can create a small flavor and try to launch instance with that flavor.

edit flag offensive delete link more
0

answered 2017-06-22 06:20:22 -0500

AmitAsh gravatar image

Hi,

I've tried removing from nova.conf the RetryFilter, and it passed this stage.

Do you know what is the purpose of the retry filter and why it blocked dispatching of the compute node?

edit flag offensive delete link more

Comments

1

The scheduler selects a node, but that node fails to boot the instance. The scheduler tries again, but this time the RetryFilter excludes that failed node.

Bernd Bausch gravatar imageBernd Bausch ( 2017-06-22 06:55:44 -0500 )edit

The problem was that the RetryFilter immediately failed w/o running other filters...

AmitAsh gravatar imageAmitAsh ( 2017-06-22 10:39:46 -0500 )edit

How do you know that?

Bernd Bausch gravatar imageBernd Bausch ( 2017-06-22 20:56:52 -0500 )edit
1

The above argument is correct about RetryFilter but it makes sense only if you are having multiple compute nodes. For single compute nodes no need to use this filter.

avinash_k_singh gravatar imageavinash_k_singh ( 2017-06-22 22:32:36 -0500 )edit

please check resource on your controller also , is it enough for create new instance ?

vgs

if VFree= <2GB may be issue

golfreeze gravatar imagegolfreeze ( 2018-02-04 02:33:47 -0500 )edit

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

1 follower

Stats

Asked: 2017-06-20 10:45:22 -0500

Seen: 3,714 times

Last updated: Jun 22 '17