I encountered the same problem, I follow the tutorial (search kairen openstack-ubuntu-newton kolla ), but the difference is that I use the kvm virtual machine as a controller , compute, network nodes.

I think the following tutorial may help you 1. About the guest host configuration Nested virtualization allows you to run a virtual machine (VM) inside another VM while still using hardware acceleration from the host. search devstack-with-nested-kvm 2. About the KVM virtual machine configuration CPU needs to configure Copy host CPU configuration search How_to_enable_nested_virtualization_in_KVM

It's also better to check neutron server.log.
When I encountered this error I sow the following neutron and nova error.

2016-03-27 19:35:52.455 1188 ERROR nova.compute.manager [-] Instance failed network setup after 1 attempt(s)
2016-03-27 19:35:52.455 1188 ERROR nova.compute.manager PortBindingFailed: Binding failed for port 

2016-03-27 19:35:52.186 2987 ERROR neutron.plugins.ml2.managers [req-d12d4244-d6b0-4c77-94ea-5b452d7b4313 40c1d949600c4da7bcda470a637643d3 12174726a6194022a36aeb2857b8b1b1 - - -] Failed to bind port 1a64b9cd-2127-4cb2-b84e-875fb7eeb2bb on host nuc1

In this case, cause of the error seems that tunnel interface between compute and network node was not created. In case you are using OVS and VXLAN for tenant network, the following tunnel interface (br-tun) and integration-bridge (br-int) must be exist.

# ovs-vsctl show
7ba02f61-9693-46fc-9a21-4768e7a3fb7f
    Bridge br-ex
        Port phy-br-ex
            Interface phy-br-ex
                type: patch
                options: {peer=int-br-ex}
        Port "eno1"
            Interface "eno1"
        Port br-ex
            Interface br-ex
                type: internal
    Bridge br-tun
        fail_mode: secure
        Port "vxlan-c0a8006f"
            Interface "vxlan-c0a8006f"
                type: vxlan
                options: {df_default="true", in_key=flow, local_ip="192.168.0.110", out_key=flow, remote_ip="192.168.0.111"}
        Port "vxlan-c0a80070"
            Interface "vxlan-c0a80070"
                type: vxlan
                options: {df_default="true", in_key=flow, local_ip="192.168.0.110", out_key=flow, remote_ip="192.168.0.112"}
        Port patch-int
            Interface patch-int
                type: patch
                options: {peer=patch-tun}
        Port br-tun
            Interface br-tun
                type: internal
    Bridge br-int
        fail_mode: secure
        Port "qr-60d2d82f-99"
            tag: 2
            Interface "qr-60d2d82f-99"
                type: internal
        Port int-br-ex
            Interface int-br-ex
                type: patch
                options: {peer=phy-br-ex}
        Port "sg-c2b3bbd4-3c"
            tag: 2
            Interface "sg-c2b3bbd4-3c"
                type: internal
        Port "sg-7ed4c1d9-8e"
            tag: 1
            Interface "sg-7ed4c1d9-8e"
                type: internal
        Port "qg-4d3615b4-85"
            tag: 3
            Interface "qg-4d3615b4-85"
                type: internal
        Port "tapc45d5edb-c9"
            tag: 2
            Interface "tapc45d5edb-c9"
                type: internal
        Port "qr-d3b7898e-5f"
            tag: 1
            Interface "qr-d3b7898e-5f"
                type: internal
        Port br-int
            Interface br-int
                type: internal
        Port "tape591e2ea-7f"
            tag: 1
            Interface "tape591e2ea-7f"
                type: internal
        Port patch-tun
            Interface patch-tun
                type: patch
                options: {peer=patch-int}
    ovs_version: "2.4.0"

If you are using Linux bridge instead of OVS, similar tunnel interface is necessary for VXLAN tenant network.

Hello How do you solved this problem I have the same and I dont found no solution yet

2015-10-05 14:02:28.474 895 INFO nova.filters [req-c5339ab5-5f10-412f-9344-749d598b8286 aac6aad372f24298a4705fa3bff60bb2 3ef932af6f884db48dabfc82ba87b3d3 - - -] Filter RetryFilter returned 0 hosts

Please check the status of your messaging service on the controller-node and maybe try to restart it. Also check all your nova config files from the compute nodes, especially the messaging part.

"No valid host was found. There are not enough hosts available." is an increadibly unhelpful error message from OpenStack. It probably means that we tried to run the instance, but got errors from all of the compute nodes. Check for errors (prefixed with TRACE) in the nova-compute log file on the compute nodes your're running.

This will show exactly what failed and hopefully explain what the fix is.

could you check if you are able to create an instance using another project..say using demo project ?

I am getting similar error after adding the second compute node. I cant see the second compute node from agent-list? I am trying to figure out why.

[root@compute2 nova]# neutron agent-list
+--------------------------------------+--------------------+----------+-------+----------------+---------------------------+
| id                                   | agent_type         | host     | alive | admin_state_up | binary                    |
+--------------------------------------+--------------------+----------+-------+----------------+---------------------------+
| 0cb8d0d4-140a-4446-add8-7881f0a07dda | DHCP agent         | network  | :-)   | True           | neutron-dhcp-agent        |
| 2a164cb6-0c6d-418a-ab7d-f68a0f3a3032 | L3 agent           | network  | :-)   | True           | neutron-l3-agent          |
| abbe20eb-8f49-43e6-a0d7-d2625ef07084 | Open vSwitch agent | network  | :-)   | True           | neutron-openvswitch-agent |
| d4e1b8a7-f826-4213-9f5f-9ab936d4f004 | Open vSwitch agent | compute1 | :-)   | True           | neutron-openvswitch-agent |
| ec116376-6d3f-4623-b5b5-78736ac41a5a | Metadata agent     | network  | :-)   | True           | neutron-metadata-agent    |
+--------------------------------------+--------------------+----------+-------+----------------+---------------------------+