Ask Your Question

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

asked 2017-04-26 10:19:33 -0500

mehdi92 gravatar image

Hello guys,

I'm stacking with this problem for a 3 days now.

I have enough ressources, but I still got this ERROR when I try to launch an instance (a small one : Cirros).

I followed the official documentation to install Openstack on 2 machines in GCE (Google Compute Engine).

I m new to this world, can you please tell which log file should I see to know where this error is coming from ?

Thank you community :)

edit retag flag offensive close merge delete


Check the nova scheduler log for messages regarding filters. You will see that a filter starts with n hosts (n>0), and ends with 0 hosts. This filter is the culprit. In Ocata, the placement service may be responsible as well.

Bernd Bausch gravatar imageBernd Bausch ( 2017-04-27 06:17:01 -0500 )edit

4 answers

Sort by ยป oldest newest most voted

answered 2017-05-08 13:29:52 -0500

arsch.sharma gravatar image

If you have enough resources on your compute node, and if neutrin is configured properly, then the reason fir this message is due to some fault in the cobtroller-compute communication. Check the nova logs for this.

edit flag offensive delete link more

answered 2017-05-09 05:02:41 -0500

Rupesh Chowdary gravatar image

updated 2017-05-09 05:03:27 -0500

First check the nova scheduler logs to figureout the initial issue. Also check the connectivity between the controller and compute server.

1.Check the all nova services are running fine. 2.Connectivity check 3. Also check the quota #openstack quota show --default 4. Verify the filters in nova.conf

edit flag offensive delete link more

answered 2017-05-09 06:04:07 -0500

Ekalaya gravatar image

I had same problem and managed to solve it by trying to launch instance without volume (in openstack dashboard choose 'No' in Create new volume option).

edit flag offensive delete link more

answered 2017-05-10 02:02:22 -0500

mehdi92 gravatar image

Thank you guys, I managed to solve this issue. I had misconfigured the endpoints of the placement service. By reviewing this, it works properly.

Thank you.

edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2017-04-26 10:19:33 -0500

Seen: 7,228 times

Last updated: May 10 '17