nova-compute fails to start when libvirtd connection is not available
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Confirmed
|
Low
|
Unassigned |
Bug Description
It is possible that starting libvirtd takes a little more time and if nova-compute is being started at the same time, it just failes because it cannot create a connection to libvirtd.
It is reproducible by calling
systemctl restart openstack-
It seems that while libvirtd is being restarted, nova tries to connect and fails. I think it would help to retry the connection several times to prevent such cases.
This seems to happen for Newton release, see packages bellow. I've just checked with Liberty and it is not possible to reproduce this behavior with Liberty. Is it caused by some thread-checking that was removed after Liberty?
# rpm -qa | grep nova
openstack-
python-
openstack-
python-
# rpm -qa | grep libvirt
libvirt-
libvirt-
libvirt-
libvirt-
libvirt-
libvirt-
libvirt-
libvirt-
libvirt-
libvirt-
libvirt-
libvirt-
libvirt-
^[[Alibvirt-
libvirt-
Changed in nova: | |
status: | In Progress → New |
assignee: | Jiri Suchomel (jsuchome) → nobody |
Fix proposed to branch: master /review. openstack. org/416928
Review: https:/