No valid hosts was found. There are not enough hosts available.

asked 2017-07-18 07:44:51 -0500

anonymous user

Anonymous

updated 2017-07-21 03:06:29 -0500

Hi, I set up OpenStack Ocata on CentOS 7. When I try to create a new instance in dashboard, I get this error: No valid hosts was found. There are not enough hosts available.

Compute node (/var/log/nova/nova-compute.log)

2017-07-21 08:52:45.701 23537 INFO nova.compute.claims [req-8eae2f17-880c-40a8-9dc9-4ec5f700ad67 f4d5b493b30f4f458569feeca2b877c3 eab26bcf12b14f1988a6aec2db3f0556 - - -] [instance: 23cfcf92-7c22-41cf-8b74-a8d10cd6c239] Attempting claim: memory 64 MB, disk 1 GB, vcpus 1 CPU
2017-07-21 08:52:45.702 23537 INFO nova.compute.claims [req-8eae2f17-880c-40a8-9dc9-4ec5f700ad67 f4d5b493b30f4f458569feeca2b877c3 eab26bcf12b14f1988a6aec2db3f0556 - - -] [instance: 23cfcf92-7c22-41cf-8b74-a8d10cd6c239] Total memory: 8191 MB, used: 512.00 MB
2017-07-21 08:52:45.702 23537 INFO nova.compute.claims [req-8eae2f17-880c-40a8-9dc9-4ec5f700ad67 f4d5b493b30f4f458569feeca2b877c3 eab26bcf12b14f1988a6aec2db3f0556 - - -] [instance: 23cfcf92-7c22-41cf-8b74-a8d10cd6c239] memory limit: 12286.50 MB, free: 11774.50 MB
2017-07-21 08:52:45.703 23537 INFO nova.compute.claims [req-8eae2f17-880c-40a8-9dc9-4ec5f700ad67 f4d5b493b30f4f458569feeca2b877c3 eab26bcf12b14f1988a6aec2db3f0556 - - -] [instance: 23cfcf92-7c22-41cf-8b74-a8d10cd6c239] Total disk: 7 GB, used: 0.00 GB
2017-07-21 08:52:45.703 23537 INFO nova.compute.claims [req-8eae2f17-880c-40a8-9dc9-4ec5f700ad67 f4d5b493b30f4f458569feeca2b877c3 eab26bcf12b14f1988a6aec2db3f0556 - - -] [instance: 23cfcf92-7c22-41cf-8b74-a8d10cd6c239] disk limit: 7.00 GB, free: 7.00 GB
2017-07-21 08:52:45.704 23537 INFO nova.compute.claims [req-8eae2f17-880c-40a8-9dc9-4ec5f700ad67 f4d5b493b30f4f458569feeca2b877c3 eab26bcf12b14f1988a6aec2db3f0556 - - -] [instance: 23cfcf92-7c22-41cf-8b74-a8d10cd6c239] Total vcpu: 8 VCPU, used: 0.00 VCPU
2017-07-21 08:52:45.705 23537 INFO nova.compute.claims [req-8eae2f17-880c-40a8-9dc9-4ec5f700ad67 f4d5b493b30f4f458569feeca2b877c3 eab26bcf12b14f1988a6aec2db3f0556 - - -] [instance: 23cfcf92-7c22-41cf-8b74-a8d10cd6c239] vcpu limit not specified, defaulting to unlimited
2017-07-21 08:52:45.706 23537 INFO nova.compute.claims [req-8eae2f17-880c-40a8-9dc9-4ec5f700ad67 f4d5b493b30f4f458569feeca2b877c3 eab26bcf12b14f1988a6aec2db3f0556 - - -] [instance: 23cfcf92-7c22-41cf-8b74-a8d10cd6c239] Claim successful
2017-07-21 08:52:45.959 23537 INFO nova.scheduler.client.report [req-8eae2f17-880c-40a8-9dc9-4ec5f700ad67 f4d5b493b30f4f458569feeca2b877c3 eab26bcf12b14f1988a6aec2db3f0556 - - -] [instance: 23cfcf92-7c22-41cf-8b74-a8d10cd6c239] Submitted allocation for instance
2017-07-21 08:52:46.328 23537 WARNING nova.virt.osinfo [req-8eae2f17-880c-40a8-9dc9-4ec5f700ad67 f4d5b493b30f4f458569feeca2b877c3 eab26bcf12b14f1988a6aec2db3f0556 - - -] Cannot find OS information - Reason: (No configuration information found for operating system Empty)
2017-07-21 08:52:46.371 23537 WARNING nova.virt.osinfo [req-8eae2f17-880c-40a8-9dc9-4ec5f700ad67 f4d5b493b30f4f458569feeca2b877c3 eab26bcf12b14f1988a6aec2db3f0556 - - -] Cannot find OS information - Reason: (No configuration information found for operating system Empty)
2017-07-21 08:52:46.641 23537 WARNING nova.virt.osinfo [req-8eae2f17-880c-40a8-9dc9-4ec5f700ad67 f4d5b493b30f4f458569feeca2b877c3 eab26bcf12b14f1988a6aec2db3f0556 - - -] Cannot find OS information - Reason: (No configuration information found for operating system Empty)
2017-07-21 08:52:46.642 23537 INFO nova.virt.libvirt.driver [req-8eae2f17-880c-40a8-9dc9-4ec5f700ad67 f4d5b493b30f4f458569feeca2b877c3 eab26bcf12b14f1988a6aec2db3f0556 - - -] [instance: 23cfcf92-7c22-41cf-8b74-a8d10cd6c239] Creating image
2017-07-21 08:52:49.318 23537 ERROR nova.compute.manager [req-8eae2f17-880c-40a8-9dc9-4ec5f700ad67 f4d5b493b30f4f458569feeca2b877c3 eab26bcf12b14f1988a6aec2db3f0556 - - -] Instance failed network setup after 1 attempt(s)
2017-07-21 08:52:49.318 23537 ERROR nova.compute.manager Traceback (most recent call last):
2017-07-21 08:52:49.318 23537 ERROR nova.compute.manager   File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 1399, in _allocate_network_async
2017-07-21 08:52:49.318 23537 ERROR nova.compute.manager     bind_host_id=bind_host_id)
2017-07-21 08:52:49.318 23537 ERROR nova.compute.manager   File "/usr/lib/python2.7/site-packages/nova/network/neutronv2/api.py", line 873, in allocate_for_instance
2017-07-21 08:52:49.318 23537 ERROR nova.compute.manager     bind_host_id, dhcp_options, available_macs)
2017-07-21 08:52:49.318 23537 ERROR nova.compute.manager   File "/usr/lib/python2.7/site-packages/nova/network/neutronv2/api.py", line 992, in _update_ports_for_instance
2017-07-21 08:52:49.318 23537 ERROR nova.compute.manager     vif.destroy()
2017-07-21 08:52:49.318 23537 ERROR nova.compute.manager   File "/usr/lib/python2 ...
(more)
edit retag flag offensive close merge delete

Comments

1

"Placement API service is not responding" Nova-compute can't reach the placement service. Could be due to wrong endpoint in catalog, or networking/firewall problems. Or something else.

Check placement endpoint and try to connect to it from compute node.

Bernd Bausch gravatar imageBernd Bausch ( 2017-07-18 08:58:24 -0500 )edit

Ok, I added ports in the firewal of controller node. It looks like the rules were cleared when I restarted the cpontroller node. Now I have another problem:

Agent healthcheck: found 3 dead agents out of 3
cloudadmin gravatar imagecloudadmin ( 2017-07-19 01:42:50 -0500 )edit

Create a new question and provide a bit of context.

Bernd Bausch gravatar imageBernd Bausch ( 2017-07-19 02:28:27 -0500 )edit