Error: Failed to launch instance [Error: No valid host was found. ].

asked 2016-12-09 16:31:37 -0500

antinode
1 ●5 ●7 ●6

updated 2016-12-12 09:18:27 -0500

THe compute node is a vm with 8GM ram, 3 cores and 250GB of disk. The image I want to use for instance is cirros using tiny flavor. So the issue isn't a lack of resources available.

/var/log/nova/nova-scheduler.log

2016-12-06 05:10:47.149 9864 INFO nova.openstack.common.service [-] Caught SIGTERM, exiting
2016-12-06 05:10:48.103 12916 AUDIT nova.service [-] Starting scheduler node (version 2014.2.4)
2016-12-06 05:10:49.013 12916 INFO oslo.messaging._drivers.impl_rabbit [req-37ad79e9-a338-4365-a026-376ed7a5bb8c ] C$
2016-12-06 05:10:49.034 12916 INFO oslo.messaging._drivers.impl_rabbit [req-37ad79e9-a338-4365-a026-376ed7a5bb8c ] C$
2016-12-06 05:12:46.225 12916 INFO nova.openstack.common.periodic_task [req-8284d20a-3f6e-46f3-95a5-9a48814a8423 Non$
2016-12-06 05:12:46.301 12916 INFO oslo.messaging._drivers.impl_rabbit [-] Connecting to AMQP server on controller:5$
2016-12-06 05:12:46.331 12916 INFO oslo.messaging._drivers.impl_rabbit [-] Connected to AMQP server on controller:56$
2016-12-06 05:12:49.505 12916 INFO nova.filters [req-8284d20a-3f6e-46f3-95a5-9a48814a8423 None] Filter RetryFilter r$lter returned 0 hosts

Nova-compute logs on the compute node is shown below:

2016-12-09 23:33:19.829 13806 AUDIT nova.compute.resource_tracker [-] Total physical ram (MB): 7983, total allocated virtual ram (MB): 1024
2016-12-09 23:33:19.829 13806 AUDIT nova.compute.resource_tracker [-] Free disk (GB): 241
2016-12-09 23:33:19.829 13806 AUDIT nova.compute.resource_tracker [-] Total usable vcpus: 3, total allocated vcpus: 0
2016-12-09 23:33:19.829 13806 AUDIT nova.compute.resource_tracker [-] PCI stats: []
2016-12-09 23:33:19.830 13806 INFO nova.compute.resource_tracker [-] Compute_service record updated for compute:compute
2016-12-09 23:33:37.722 13806 INFO nova.virt.libvirt.imagecache [-] image d72b6577-224f-427a-82ab-d8231c4b2711 at (/var/lib/nova/instances/_base/a893a8504f71e403a02df5401bd0fb3e08bd0933): checking
2016-12-09 23:33:37.722 13806 INFO nova.virt.libvirt.imagecache [-] image d72b6577-224f-427a-82ab-d8231c4b2711 at (/var/lib/nova/instances/_base/a893a8504f71e403a02df5401bd0fb3e08bd0933): in use: on this node 1 local, 0 on other nodes sharing this instance storage
2016-12-09 23:33:37.774 13806 INFO nova.virt.libvirt.imagecache [-] Active base files: /var/lib/nova/instances/_base/a893a8504f71e403a02df5401bd0fb3e08bd0933
2016-12-09 23:34:20.698 13806 AUDIT nova.compute.resource_tracker [-] Auditing locally available compute resources
2016-12-09 23:34:20.818 13806 AUDIT nova.compute.resource_tracker [-] Total physical ram (MB): 7983, total allocated virtual ram (MB): 1024
2016-12-09 23:34:20.819 13806 AUDIT nova.compute.resource_tracker [-] Free disk (GB): 241
2016-12-09 23:34:20.819 13806 AUDIT nova.compute.resource_tracker [-] Total usable vcpus: 3, total allocated vcpus: 0
2016-12-09 23:34:20.819 13806 AUDIT nova.compute.resource_tracker [-] PCI stats: []
2016-12-09 23:34:20.820 13806 INFO nova.compute.resource_tracker [-] Compute_service record updated for compute:compute
2016-12-09 23:34:21.397 13806 WARNING nova.compute.manager [-] While synchronizing instance power states, found 1 instances in the database and 0 instances on the hypervisor.

After turning debug to true in nova.conf, I get the following in nova-scheduler.log

2016-12-06 06:18:17.314 12916 INFO nova.openstack.common.service [-] Caught SIGTERM, exiting
2016-12-06 06:18:18.188 14015 AUDIT nova.service [-] Starting scheduler node (version 2014.2.4 ...

(more)

edit retag flag offensive close merge delete

Comments

I am not sure how to interpret the following line from nova-compute log on compute node

2016-12-09 23:34:21.397 13806 WARNING nova.compute.manager [-] While synchronizing instance power states, found 1 instances in the database and 0 instances on the hypervisor.

antinode ( 2016-12-10 11:04:19 -0500 )edit

wow this error again try to change the hypervisor (from kvm to qemu) in the nova.conf file under /etc/nova [libvirt] virt_type =qemu then restart nova services

yas ( 2016-12-12 11:19:44 -0500 )edit

@yas already been done, I did that when deploying openstack in /etc/nova/nova-compute.conf on compute node. Since then ive restarted nova multiple times.

antinode ( 2016-12-12 11:37:55 -0500 )edit

Please post your neutron logs.. This issue can be of neutron port binding issue.. Instance cant be able to create its port in your compute node..

vathanlal ( 2016-12-14 07:41:57 -0500 )edit

@vathanlal You were right, it had something to do with network ports. I still don't know why admin ports are down though.

antinode ( 2016-12-14 16:30:40 -0500 )edit

add a comment

2 answers

Sort by » oldest newest most voted

answered 2016-12-09 18:09:26 -0500

Bernd Bausch

7773 ●46 ●79 ●160 https://www.linkedin.c...

updated 2016-12-09 20:58:17 -0500

The message means that this host was found not to correspond to the needs of the instance, then, at the next attempt to find a host for the same instance, the scheduler discarded the host because it was already found unsuitable.

Configure debug logging, so that the scheduler tells you which filter doesn't like this host.

edit flag offensive delete link

Comments

It sounds that the building fails and then it goes for retry and fails again. Check nova-compute and Libvirt/QEMU stuff- log of nova-compute on your Compute Hosts and Libvirt/QEMU logs

volenbovsky ( 2016-12-10 08:32:14 -0500 )edit

I added the logs for nova-compute on compute node. I checked the Libvirt/qemu stuff using the openstack documentation and it looks fine.

antinode ( 2016-12-10 10:30:48 -0500 )edit

Hmmm, 1) Search for "nova.scheduler.filters.retry_filter" in this site/Google and check if anything applies to you 2) Use --availability-zone , availability zone and Compute Host (like --availability-zone nova:compute) to avoid the scheduler altogether. That likely will reveal something else

volenbovsky ( 2016-12-10 15:50:40 -0500 )edit

INFO nova.filters [req-8284d20a-3f6e-46f3-95a5-9a48814a8423 None] Filter RetryFilter r$lter returned 0 hosts. check for nova service-listnova hypervisor-list

Bipin ( 2016-12-12 00:02:27 -0500 )edit

nova service-list:

nova-cert        | controller | internal | enabled | up
nova-consoleauth | controller | internal | enabled | up
nova-scheduler   | controller | internal | enabled | up
nova-conductor   | controller | internal | enabled | up 
nova-compute     | compute    | nova     | enabled | up

antinode ( 2016-12-12 09:15:57 -0500 )edit

see more comments

answered 2016-12-12 12:21:16 -0500

antinode
1 ●5 ●7 ●6

updated 2016-12-14 16:29:35 -0500

So I am able to launch instances on demo account but not admin. For the demo account network, all the ports are up, but for admin all the ports are down.

Does anyone know why the admin network ports are down?

edit flag offensive delete link

Comments

How did you create your private network?? by sourcing demo credential or admin credentials?? Which release of Openstack you are using??

vathanlal ( 2016-12-15 02:03:45 -0500 )edit

@vathanlal deployed juno using the network setup instructions in juno ubuntu guide

antinode ( 2016-12-17 19:29:12 -0500 )edit

add a comment

Error: Failed to launch instance [Error: No valid host was found. ].

Comments

2 answers

Comments

Comments

Get to know Ask OpenStack

Question Tools

Stats

Related questions

Feedback About This Page

OpenStack

Community

Documentation

Branding & Legal

Error: Failed to launch instance [Error: No valid host was found. ]. edit

Comments

2 answers

Comments

Comments

Get to know Ask OpenStack

Question Tools

Stats

Related questions

Feedback About This Page

OpenStack

Community

Documentation

Branding & Legal

Error: Failed to launch instance [Error: No valid host was found. ].