Ask Your Question
6

Error: No valid host was found. There are not enough hosts available [closed]

asked 2015-08-07 16:29:35 -0500

Anario gravatar image

updated 2015-08-11 06:28:21 -0500

Any Idea ? image description

[UPDATE]

this is my nova-compute.log

2015-08-09 15:11:43.367 5876 INFO nova.compute.resource_tracker [-] Compute_service record updated for compute1:compute1
2015-08-09 15:12:43.052 5876 AUDIT nova.compute.resource_tracker [-] Auditing locally available compute resources
2015-08-09 15:12:43.364 5876 AUDIT nova.compute.resource_tracker [-] Total physical ram (MB): 48254, total allocated virtual ram (MB): 2560
2015-08-09 15:12:43.365 5876 AUDIT nova.compute.resource_tracker [-] Free disk (GB): 888
2015-08-09 15:12:43.365 5876 AUDIT nova.compute.resource_tracker [-] Total usable vcpus: 32, total allocated vcpus: 0

also this from dashboard image description

edit retag flag offensive reopen merge delete

Closed for the following reason duplicate question by Anario
close date 2015-08-11 15:52:42.563065

Comments

could you show nova error logs?

Sihan gravatar imageSihan ( 2015-08-07 22:29:49 -0500 )edit

Mate please post your error from the log files. You should post your output from this file. /var/log/nova-compute.log from the compute node.

RAHUL1603 gravatar imageRAHUL1603 ( 2015-08-11 07:24:36 -0500 )edit

See if you have enough space in your compute node. If that's positive, see if you have any ServerAntiAffinityGroup set which can hold you back from launching two instances under the same group.

deepaks gravatar imagedeepaks ( 2016-11-08 03:17:26 -0500 )edit

3 answers

Sort by ยป oldest newest most voted
2

answered 2015-08-11 05:09:32 -0500

foexle gravatar image

Hi,

please check with

nova service-list

if your compute agents are all in a good state. Next you should check if the hypervisor

nova hypervisor-show

have enough free resources for your used flavor. In addition check your pipeline of your Nova scheduler ( normally filter pipeline) if there any useless entries are present

Your log looks like the agent is running well and give usage informations to the collector. So check if these data are really present in the database (hypervisor stats).

A good idea is to check the nova-scheduler log to get maybe more informations.

Cheers Heiko

edit flag offensive delete link more
0

answered 2015-08-11 15:52:20 -0500

Anario gravatar image

I fix it by configuring the network

edit flag offensive delete link more

Comments

What u mean by Fix the network configuration ?? can you please more clarify

Hosam gravatar imageHosam ( 2015-09-17 21:42:15 -0500 )edit

I got this error when i configured my local network and public network wrong.

Anario gravatar imageAnario ( 2015-09-28 03:31:13 -0500 )edit

Could you please explain how did you do it exactly? I am facing the exact same problem. But don't know how to resolve it. All the nova services are running successfully and no error is reported in their logs.

fhussain gravatar imagefhussain ( 2015-10-12 01:39:05 -0500 )edit

having the same exact issue, still did not get how you managed to fix it ? can you please explain ?

kobig gravatar imagekobig ( 2016-02-17 07:58:49 -0500 )edit

I tried to remove public network before starting; it works

Nhutumdai gravatar imageNhutumdai ( 2016-02-29 04:43:20 -0500 )edit

Remove public network from??

larkinscarvalho gravatar imagelarkinscarvalho ( 2016-04-04 18:39:03 -0500 )edit

Can you explain more please coz' I am running this same error

Sofiane68 gravatar imageSofiane68 ( 2016-04-13 05:22:05 -0500 )edit
0

answered 2015-08-09 03:27:12 -0500

RAHUL1603 gravatar image

Hi Probably,

Your compute nodes are not able to communicate properly with the controller node. Please check these logs /var/log/nova-compute.log to ensure. If it shows connected to AMPQ that means you have a good connectivity.

Apart from this if you examine the above logs you will find a detailed error of why the instance is going into an error state.

Regards Rahul Singh

edit flag offensive delete link more

Comments

I've got this error when I login with Admin account. When I login with demo account everything working like charm and I can create Instance. My question is why Admin can not launch Instance and receive this error?

Ahmed Morgan gravatar imageAhmed Morgan ( 2015-08-18 12:15:15 -0500 )edit

Get to know Ask OpenStack

Resources for moderators

Question Tools

4 followers

Stats

Asked: 2015-08-07 16:29:35 -0500

Seen: 59,466 times

Last updated: Aug 11 '15