yahoo-eng-team team mailing list archive

[Jiri Suchomel <jsuchome@xxxxxxxx>]

Public bug reported:

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-nova-compute && systemctl restart libvirtd

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-nova-12.0.6~a0~dev2-11.17.noarch
python-novaclient-2.30.1-12.1.noarch
openstack-nova-compute-12.0.6~a0~dev2-11.17.noarch
python-nova-12.0.6~a0~dev2-11.17.noarch

# rpm -qa | grep libvirt
libvirt-daemon-driver-secret-1.2.18.4-18.2.x86_64
libvirt-daemon-driver-lxc-1.2.18.4-18.2.x86_64
libvirt-client-1.2.18.4-18.2.x86_64
libvirt-daemon-driver-interface-1.2.18.4-18.2.x86_64
libvirt-python-1.2.18-1.2.x86_64
libvirt-daemon-1.2.18.4-18.2.x86_64
libvirt-daemon-driver-nodedev-1.2.18.4-18.2.x86_64
libvirt-daemon-config-nwfilter-1.2.18.4-18.2.x86_64
libvirt-1.2.18.4-18.2.x86_64
libvirt-daemon-driver-storage-1.2.18.4-18.2.x86_64
libvirt-daemon-driver-network-1.2.18.4-18.2.x86_64
libvirt-daemon-driver-qemu-1.2.18.4-18.2.x86_64
libvirt-daemon-driver-libxl-1.2.18.4-18.2.x86_64
^[[Alibvirt-daemon-driver-nwfilter-1.2.18.4-18.2.x86_64
libvirt-daemon-config-network-1.2.18.4-18.2.x86_64

** Affects: nova
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1654207

Title:
  nova-compute fails to start when libvirtd connection is not available

Status in OpenStack Compute (nova):
  New

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-nova-compute && systemctl restart libvirtd

  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-nova-12.0.6~a0~dev2-11.17.noarch
  python-novaclient-2.30.1-12.1.noarch
  openstack-nova-compute-12.0.6~a0~dev2-11.17.noarch
  python-nova-12.0.6~a0~dev2-11.17.noarch

  # rpm -qa | grep libvirt
  libvirt-daemon-driver-secret-1.2.18.4-18.2.x86_64
  libvirt-daemon-driver-lxc-1.2.18.4-18.2.x86_64
  libvirt-client-1.2.18.4-18.2.x86_64
  libvirt-daemon-driver-interface-1.2.18.4-18.2.x86_64
  libvirt-python-1.2.18-1.2.x86_64
  libvirt-daemon-1.2.18.4-18.2.x86_64
  libvirt-daemon-driver-nodedev-1.2.18.4-18.2.x86_64
  libvirt-daemon-config-nwfilter-1.2.18.4-18.2.x86_64
  libvirt-1.2.18.4-18.2.x86_64
  libvirt-daemon-driver-storage-1.2.18.4-18.2.x86_64
  libvirt-daemon-driver-network-1.2.18.4-18.2.x86_64
  libvirt-daemon-driver-qemu-1.2.18.4-18.2.x86_64
  libvirt-daemon-driver-libxl-1.2.18.4-18.2.x86_64
  ^[[Alibvirt-daemon-driver-nwfilter-1.2.18.4-18.2.x86_64
  libvirt-daemon-config-network-1.2.18.4-18.2.x86_64

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1654207/+subscriptions