Ask Your Question
0

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

asked 2014-06-05 15:18:14 -0500

danoreilly gravatar image

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

Trying to launch an instance via the dashboard.

edit retag flag offensive reopen merge delete

Closed for the following reason the question is answered, right answer was accepted by danoreilly
close date 2014-06-06 21:30:40.176062

Comments

What is the output of nova-manage service list? Did you launched it from Dashboard or CLI?

Itzik gravatar imageItzik ( 2014-06-05 16:14:27 -0500 )edit

2 answers

Sort by ยป oldest newest most voted
1

answered 2014-06-05 21:16:29 -0500

dbaxps gravatar image
You just try to overcome the quota . On Fedora 20 it's 5 VMs on each Compute Node.
The only option I can use drop old one && restart nova-compute service. Then veify Hypervisor
Section , logged as admin.
edit flag offensive delete link more
3

answered 2014-06-05 21:49:13 -0500

larsks gravatar image

The "no valid host was found" error means the scheduler was unable to find a compute host with the resources necessary to boot your instance. This can happen legitimately if your instance requires more CPU cores or memory than is currently available, but it can also happen if there is a configuration issues on your compute hosts that makes them unavailable to the scheduler.

The first step is to make sure you're not running into an actual resource problem. If you're confident that you are not attempting to use more compute resources than you have available, the next step is to run nova-manage service list, which will produce something like this:

Binary           Host                                 Zone             Status     State Updated_At
nova-consoleauth mycontroller                         internal         enabled    :-)   2014-06-06 02:44:41
nova-scheduler   mycontroller                         internal         enabled    :-)   2014-06-06 02:44:41
nova-conductor   mycontroller                         internal         enabled    :-)   2014-06-06 02:44:37
nova-cert        mycontroller                         internal         enabled    :-)   2014-06-06 02:44:41
nova-compute     mycomputenode                        nova             enabled    :-)   2014-06-06 02:44:34

You want to see :-) for all of your compute nodes. If instead you see:

nova-compute     mycomputenode                        nova             enabled    XXX   2014-06-06 02:46:14

This indicates that your compute node is not properly communicating with the rest of your environment. The first place to look in this case is in /var/log/nova/compute.log on your compute host.

If nova-manage service list reports :-) for all your compute nodes, then you probably want to start by focusing on /var/log/nova/scheduler.log on your controller, which may have more information about why a valid compute host was not available.

Hopefully these steps will help you get closer to diagnosing your problem.

edit flag offensive delete link more

Comments

Ah, yes, it did. When I used nova-manage, I got:


# nova-manage service list
Binary Host Zone Status State Updated_At
nova-consoleauth tm1cldctll01 internal enabled :-) 2014-06-06 13:21:47
nova-conductor tm1cldctll01 internal enabled :-) 2014-06-06 13:21:44
nova-scheduler tm1cldctll01 internal enabled :-) 2014-06-06 13:21:46
nova-cert tm1cldctll01 internal enabled :-) 2014-06-06 13:21:46
nova-compute tm1cldcmpl03 nova enabled XXX 2014-06-02 21:09:42
nova-compute tm1cldcmpl02 nova enabled :-) 2014-06-06 13:21:42

danoreilly gravatar imagedanoreilly ( 2014-06-06 08:44:21 -0500 )edit

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2014-06-05 15:18:14 -0500

Seen: 8,107 times

Last updated: Jun 05 '14