Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

nova scheduler: No valid host was found. There are not enough hosts available.

We have deployed multi-node OpenStack (Juno: http://docs.openstack.org/juno/install-guide/install/apt/content/ch_nova.html) based on Virtualbox. Our compute and network nodes are on guest VMs, whereas our controller node is on host machine. We are facing an error, "No valid host was found. There are not enough hosts available" when we try to launch an instance. According to nova-scheduler logs, the host controller is failing. We presume that it might be an issue of compute hypervisor which is not shown in hypervisor-list. Any idea how this issue can be resolved?

nova service-list

+----+------------------+------------+----------+---------+-------+----------------------------+-----------------+
| Id | Binary           | Host       | Zone     | Status  | State | Updated_at                 | Disabled Reason |
+----+------------------+------------+----------+---------+-------+----------------------------+-----------------+
| 1  | nova-cert        | controller | internal | enabled | up    | 2016-11-01T14:53:57.000000 | -               |
| 2  | nova-consoleauth | controller | internal | enabled | up    | 2016-11-01T14:53:58.000000 | -               |
| 3  | nova-scheduler   | controller | internal | enabled | up    | 2016-11-01T14:53:59.000000 | -               |
| 4  | nova-conductor   | controller | internal | enabled | up    | 2016-11-01T14:53:59.000000 | -               |
| 5  | nova-compute     | compute    | nova     | enabled | up    | 2016-11-01T14:54:03.000000 | -               |
| 6  | nova-compute     | controller | nova     | enabled | up    | 2016-11-01T14:53:59.000000 | -               |
+----+------------------+------------+----------+---------+-------+----------------------------+-----------------+

nova hypervisor-list

+----+---------------------+-------+---------+
| ID | Hypervisor hostname | State | Status  |
+----+---------------------+-------+---------+
| 1  | controller          | up    | enabled |
+----+---------------------+-------+---------+

2016-11-02 00:06:46.832 10638 WARNING nova.scheduler.filters.compute_filter [req-710be1c4-185e-425d-bc34-8e8b47183c8d 9224f04451e74a8daafb9fba6a7ac047 03a58bc4d34c4c0e9c52b679cd659d6c - - -] (controller, controller) ram:6848 disk:360448 io_ops:0 instances:1 has not been heard from in a while 2016-11-02 00:06:46.832 10638 INFO nova.filters [req-710be1c4-185e-425d-bc34-8e8b47183c8d 9224f04451e74a8daafb9fba6a7ac047 03a58bc4d34c4c0e9c52b679cd659d6c - - -] Filter ComputeFilter returned 0 hosts 2016-11-02 00:06:46.832 10638 DEBUG nova.scheduler.filter_scheduler [req-710be1c4-185e-425d-bc34-8e8b47183c8d 9224f04451e74a8daafb9fba6a7ac047 03a58bc4d34c4c0e9c52b679cd659d6c - - -] There are 0 hosts available but 1 instances requested to build. select_destinations /usr/lib/python2.7/dist-packages/nova/scheduler/filter_scheduler.py:77

nova scheduler: No valid host was found. There are not enough hosts available.

We have deployed multi-node OpenStack (Juno: http://docs.openstack.org/juno/install-guide/install/apt/content/ch_nova.html) based on Virtualbox. Our compute and network nodes are on guest VMs, whereas our controller node is on host machine. We are facing an error, "No valid host was found. There are not enough hosts available" when we try to launch an instance. According to nova-scheduler logs, the host controller is failing. We presume that it might be an issue of compute hypervisor which is not shown in hypervisor-list. Any idea how this issue can be resolved?

nova service-list

+----+------------------+------------+----------+---------+-------+----------------------------+-----------------+
| Id | Binary           | Host       | Zone     | Status  | State | Updated_at                 | Disabled Reason |
+----+------------------+------------+----------+---------+-------+----------------------------+-----------------+
| 1  | nova-cert        | controller | internal | enabled | up    | 2016-11-01T14:53:57.000000 | -               |
| 2  | nova-consoleauth | controller | internal | enabled | up    | 2016-11-01T14:53:58.000000 | -               |
| 3  | nova-scheduler   | controller | internal | enabled | up    | 2016-11-01T14:53:59.000000 | -               |
| 4  | nova-conductor   | controller | internal | enabled | up    | 2016-11-01T14:53:59.000000 | -               |
| 5  | nova-compute     | compute    | nova     | enabled | up    | 2016-11-01T14:54:03.000000 | -               |
| 6  | nova-compute     | controller | nova     | enabled | up    | 2016-11-01T14:53:59.000000 | -               |
+----+------------------+------------+----------+---------+-------+----------------------------+-----------------+

nova hypervisor-list

+----+---------------------+-------+---------+
| ID | Hypervisor hostname | State | Status  |
+----+---------------------+-------+---------+
| 1  | controller          | up    | enabled |
+----+---------------------+-------+---------+

2016-11-02 00:06:46.832 10638 WARNING nova.scheduler.filters.compute_filter [req-710be1c4-185e-425d-bc34-8e8b47183c8d 9224f04451e74a8daafb9fba6a7ac047 03a58bc4d34c4c0e9c52b679cd659d6c - - -] (controller, controller) ram:6848 disk:360448 io_ops:0 instances:1 has not been heard from in a while 2016-11-02 00:06:46.832 10638 INFO nova.filters [req-710be1c4-185e-425d-bc34-8e8b47183c8d 9224f04451e74a8daafb9fba6a7ac047 03a58bc4d34c4c0e9c52b679cd659d6c - - -] Filter ComputeFilter returned 0 hosts 2016-11-02 00:06:46.832 10638 DEBUG nova.scheduler.filter_scheduler [req-710be1c4-185e-425d-bc34-8e8b47183c8d 9224f04451e74a8daafb9fba6a7ac047 03a58bc4d34c4c0e9c52b679cd659d6c - - -] There are 0 hosts available but 1 instances requested to build. select_destinations /usr/lib/python2.7/dist-packages/nova/scheduler/filter_scheduler.py:77

/usr/lib/python2.7/dist-packages/nova/scheduler/filter_scheduler.py:77