nova-compute error
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Hi All,
I have a rocky setup. I am unable to launch instances on one of the compute nodes.
I see the following error in the conductor logs and the libvirtd service on the compute. The host is ubuntu 18.04:
------------------
File "/openstack/
raise exception.
NoValidHost: No valid host was found.
2020-03-20 05:31:09.006 35363 ERROR nova.conductor.
2020-03-20 05:31:09.006 35363 ERROR nova.conductor.
2020-03-20 05:31:09.006 35363 ERROR nova.conductor.
2020-03-20 05:31:09.006 35363 ERROR nova.conductor.
2020-03-20 05:31:09.006 35363 ERROR nova.conductor.
2020-03-20 05:31:09.006 35363 ERROR nova.conductor.
2020-03-20 05:31:09.006 35363 ERROR nova.conductor.
2020-03-20 05:31:09.006 35363 ERROR nova.conductor.
2020-03-20 05:31:09.006 35363 ERROR nova.conductor.
2020-03-20 05:31:09.006 35363 ERROR nova.conductor.
2020-03-20 05:31:09.006 35363 ERROR nova.conductor.
2020-03-20 05:31:09.006 35363 ERROR nova.conductor.
2020-03-20 05:31:09.006 35363 ERROR nova.conductor.
2020-03-20 05:31:09.006 35363 ERROR nova.conductor.
2020-03-20 05:31:09.006 35363 ERROR nova.conductor.
2020-03-20 05:31:09.006 35363 ERROR nova.conductor.
2020-03-20 05:31:09.006 35363 ERROR nova.conductor.
2020-03-20 05:31:09.006 35363 ERROR nova.conductor.
2020-03-20 05:31:09.006 35363 ERROR nova.conductor.
2020-03-20 05:31:09.006 35363 ERROR nova.conductor.
2020-03-20 05:31:09.006 35363 ERROR nova.conductor.
2020-03-20 05:31:09.006 35363 ERROR nova.conductor.
2020-03-20 05:31:09.006 35363 ERROR nova.conductor.
2020-03-20 05:31:09.006 35363 ERROR nova.conductor.
2020-03-20 05:31:09.006 35363 ERROR nova.conductor.
2020-03-20 05:31:09.006 35363 ERROR nova.conductor.
2020-03-20 05:31:09.006 35363 ERROR nova.conductor.
2020-03-20 05:31:09.006 35363 ERROR nova.conductor.
2020-03-20 05:31:09.006 35363 ERROR nova.conductor.
2020-03-20 05:31:09.006 35363 ERROR nova.conductor.
2020-03-20 05:31:09.006 35363 ERROR nova.conductor.
2020-03-20 05:31:09.006 35363 ERROR nova.conductor.
2020-03-20 05:31:09.006 35363 ERROR nova.conductor.
2020-03-20 05:31:09.390 35363 WARNING nova.scheduler.
-------
This is the error on the nova-compute service on that compute node:
-------------
2020-03-20 01:44:24.158 6193 ERROR nova.compute.
------------------
This is the status of the libvirtd service on that compute node:
-------
Mar 19 04:32:04 b2a-1 libvirtd[5732]: internal error: Failed to start QEMU binary /usr/bin/
Mar 19 04:32:04 b2a-1 libvirtd[5732]: Failed to probe capabilities for /usr/bin/
Mar 19 04:32:04 b2a-1 libvirtd[5732]: internal error: Failed to start QEMU binary /usr/bin/
Mar 19 04:32:04 b2a-1 libvirtd[5732]: Failed to probe capabilities for /usr/bin/
Mar 19 04:32:08 b2a-1 libvirtd[5732]: internal error: Failed to start QEMU binary /usr/bin/
Mar 19 04:32:08 b2a-1 libvirtd[5732]: Failed to probe capabilities for /usr/bin/
Mar 19 04:32:08 b2a-1 libvirtd[5732]: internal error: Failed to start QEMU binary /usr/bin/
Mar 19 04:32:08 b2a-1 libvirtd[5732]: Failed to probe capabilities for /usr/bin/
Mar 19 04:32:14 b2a-1 libvirtd[5732]: Failed to open file '/sys/class/
Mar 19 04:32:14 b2a-1 libvirtd[5732]: unable to read: /sys/class/
-------
Please help me out with this issue.
Thanks
Kumar
This seems like a QEMU problem that leads to nova not knowing how much resources the hypervisor has.