Ask Your Question
4

Openstack Icehouse instance launch ERROR "No valid host was found"

asked 2014-06-24 05:48:39 -0600

anonymous user

Anonymous

=========================== Error: Failed to launch instance "test": Please try again later [Error: No valid host was found. ].

File "/usr/lib/python2.6/site-packages/nova/scheduler/filter_scheduler.py", line 108, in schedule_run_instance raise exception.NoValidHost(reason="")

edit retag flag offensive close merge delete

Comments

check whether the compute node is functional and accessible from controller. cross check the host entries.

rajavin parvai gravatar imagerajavin parvai ( 2014-06-24 08:07:02 -0600 )edit

2 answers

Sort by ยป oldest newest most voted
5

answered 2014-06-24 08:55:00 -0600

SGPJ gravatar image

Please look at the nova-api.log and nova-scheduler.log. The NoValidHost error indicates that the scheduler was unable to locate a compute node with enough available vCPUs, RAM, or HDD space to host an instance of the selected flavour. Ensure that the nova-compute service is active on the compute node and that the compute node has enough available resources to host the instance being launched. Note that the baremetal-* commands are only relevant to users of the baremetal driver. Please look at the nova-api.log and nova-scheduler.log. Check whether rabbitmq is running on controller. Appropriate password set for rabbitmq in nova.conf on controller and compute. Compute should be connecting to rabitmq on controller itself. You can set the flag scheduler_default_filters=AllHostsFilter in nova.conf. Restart the all service on controller and compute.

edit flag offensive delete link more

Comments

I have the same problem and I saw in my nova-scheduler.log that there are several odd messages:

Host has more disk space than database expected (96gb > 62gb)
No hosts matched due to not matching 'force_hosts' value of 'x217.boku.ac.at'
Filter RetryFilter returned 0 hosts
kermit666 gravatar imagekermit666 ( 2014-08-25 17:16:01 -0600 )edit
0

answered 2015-11-10 14:06:12 -0600

JPF gravatar image

I realize this is an old post, but I came here via Google as I was having similar troubles trying to intentionally launch an instance on a specific hypervisor and getting the 'force_hosts' error. The problem I ran into was that the "host" name can be different than the "hypervisor" name. The nova boot command is looking for the "host" name and not the hypervisor name (or hypervisor id).

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

2 followers

Stats

Asked: 2014-06-24 05:48:39 -0600

Seen: 18,603 times

Last updated: Jun 24 '14