No valid host was found

asked 2013-12-25 16:26:04 -0600

Ron L. gravatar image

updated 2014-01-22 15:12:35 -0600

Evgeny gravatar image

Latest update:

| fault                                | {u'message': u'No valid host was found. ', u'code': 500, u'created

I've pinpointed the error to this message. I found a link that said this was due to insufficient CPU/RAM/resources. This is a fresh node with 72GB RAM and 12 core so obviously nova-compute isn't reading the resources correctly. Nova-compute is active in the services list. No errors I can find in compute.log. Where should I go from here?

Hi, I have an RDO single-node, all-in-one install. Creating instances in Havana end up with an "Error" for the instance Status. When I check /var/lib/nova/instances, there are no files except for an empty "lost+found" folder.

Running virsh list --all returns an empty list. There are no errors in compute.log. Any idea where I should look/what can be done?

UPDATE: This error was found in scheduler.log

2013-12-24 15:29:56.926 18366 DEBUG nova.openstack.common.service [-] fatal_deprecations             = False log_opt_values /usr/lib/python2.6/site-packages/oslo/config/
2013-12-24 15:29:56.926 18366 DEBUG nova.openstack.common.service [-] fatal_exception_format_errors  = False log_opt_values /usr/lib/python2.6/site-packages/oslo/config/

UPDATE2: How can I get service network running? is it important?

[root@test nova(keystone_admin)]# nova host-list
| host_name                 | service     | zone |
| rdotest | cert        | nova |
| rdotest | conductor   | nova |
| rdotest | consoleauth | nova |
| rdotest | compute     | nova |
| rdotest | scheduler   | nova |
edit retag flag offensive close merge delete

2 answers

Sort by ยป oldest newest most voted

answered 2013-12-26 01:43:34 -0600

dheeru gravatar image
It is difficult to tell from the on line error. Please look at the following files and see what is the error. Is this multi-node setup or single node-setup. If it is multi node setup, please look for either of following logs in all the compute boxes.

You can also look for detail troubleshooting at following link.
edit flag offensive delete link more

answered 2014-04-23 17:53:05 -0600

bigperk gravatar image

updated 2014-04-23 18:05:58 -0600

I have had this experience, and what I found was my NFS share had old lock/ stuff, from creating, tearing down, re-creating, tearing down. I'm not certain this is your case, but I found clearing all the old stuff from my NFS mounted /var/lib/nova/instances/ directory fixed my case of this error.

the more I look at my logs, and your case, I think they differ. my error looked like:

and it was cleared by just removing all the files in the nfs share mounted on /var/lib/nova/instances which were left by previous adventures into testing a small cloud setup. (which did not all end "well" leaving behind detritus

edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2013-12-25 16:26:04 -0600

Seen: 6,193 times

Last updated: Apr 23 '14