Ask Your Question
0

Failed to launch instance. libvirt error and no hosts found

asked 2017-11-01 11:08:35 -0500

jcorkey gravatar image

updated 2017-11-01 15:01:46 -0500

I have openstack pike that I deployed using kolla. All services are running in containers on my controller node and compute node. I can access the horizon dashboard and create images, flavors, networks, routers, etc etc. But I am getting an error when trying to launch an instance!

Below is the error I get from nova-copmute logs:

ERROR nova.compute.manager [instance: 3af11e19-b4f8-452a-8f3d-3d659be050bd] libvirtError: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

It is metioning something about libvirt. libvirt is down or in-active on my controller node but it is UP and running on my compute node.

Also the main error that shows up on the horizon dashboard when I try to launch an instance is:

Error: Failed to perform requested operation on instance "sf", the instance has an error status: Please try again later [Error: No valid host was found. There are not enough hosts available.].

Below Is the error in the libvirtd.log file on the compute node:

2017-11-01 18:46:09.362+0000: 30348: info : libvirt version: 3.2.0, package: 14.el7_4.3 (CentOS BuildSystem <http://bugs.centos.org>, 2017-09-07-11:27:44, c1bm.rdu2.centos.org)
2017-11-01 18:46:09.362+0000: 30348: info : hostname: openstackcompute.glv.internal
2017-11-01 18:46:09.362+0000: 30348: error : virDBusCall:1570 : error from service: CanSuspend: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the re
ply, the reply timeout expired, or the network connection was broken.
2017-11-01 18:46:09.362+0000: 30348: warning : virQEMUCapsInit:1142 : Failed to get host power management capabilities
2017-11-01 18:46:39.795+0000: 30348: error : virDBusCall:1570 : error from service: CanSuspend: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the re
ply, the reply timeout expired, or the network connection was broken.
2017-11-01 18:46:39.795+0000: 30348: warning : virLXCDriverCapsInit:87 : Failed to get host power management capabilities
2017-11-01 18:47:09.842+0000: 30335: error : virDBusCall:1570 : error from service: CanSuspend: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the re
ply, the reply timeout expired, or the network connection was broken.
2017-11-01 18:47:09.842+0000: 30335: warning : virQEMUCapsInit:1142 : Failed to get host power management capabilities
2017-11-01 19:43:29.111+0000: 30335: error : virSystemdCreateMachine:418 : Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeou
t expired, or the network connection was broken.

My distribution is centos 7. I am using tag 5.0.1 for the container images. Any ideas of how to fix this error?

edit retag flag offensive close merge delete

Comments

Hi, i guess you may need to check nova config virt_type under [libvirt] section .Is that qemu ?

Praveen N gravatar imagePraveen N ( 2017-11-02 02:28:11 -0500 )edit

Is libvirt configured correctly? You'll have to get libvirt up and running before nova will work.

eblock gravatar imageeblock ( 2017-11-02 06:15:34 -0500 )edit

The documentation says make sure that libvirtd is NOT running on all target nodes...I deployed openstack using kolla. Here is the doc that says to turn it off on all target nodes for a deployment: https://docs.openstack.org/kolla-ansible/latest/user/quickstart.html

Im so confused

jcorkey gravatar imagejcorkey ( 2017-11-02 07:04:28 -0500 )edit

Don't let me confuse you, I'm not familiar with kolla and docker, so you're are right about the target nodes, but it also says: "Please disable libvirt on any machines that will be deployment targets. Only one copy of libvirt may be running at a time." I don't know what the target nodes are...

eblock gravatar imageeblock ( 2017-11-03 04:03:54 -0500 )edit

maybe someone with kolla experience will be able to help you, sorry.

eblock gravatar imageeblock ( 2017-11-03 04:05:30 -0500 )edit

2 answers

Sort by ยป oldest newest most voted
1

answered 2018-02-07 20:08:50 -0500

chrishoge gravatar image

You need configure selinux, in /etc/selinux/config, from 'enabled' to 'permissive' on the compute hosts. Kolla does not have full support for selinux on CentOS as of this writing (stable/pike).

edit flag offensive delete link more

Comments

This worked for me, THANKS I just ran "setenforce permissive" on all nodes

Klimber gravatar imageKlimber ( 2018-03-28 18:27:20 -0500 )edit
0

answered 2018-02-08 01:10:55 -0500

Just check whether qemu-kvm service is running on your compute/hypervisor nodes

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2017-11-01 11:08:35 -0500

Seen: 330 times

Last updated: Feb 08