[Bug 1411278] Re: nova-compute doesn't reconnect to libvirtd

James Page james.page at ubuntu.com
Thu Feb 2 11:33:10 UTC 2017

OK so I'm pretty sure that newer nova-compute versions do reconnect to
libvirt if connections are lost (I just checked on a newton cloud,
restarting libvirt did not cause any side-effects in nova, and the
compute unit is still reporting as active and is functional).

This is possibly an issue that impacted older nova versions; either way
this is not a charm problem, so adding a task for nova in Ubuntu
(icehouse is no longer supported upstream).

** Changed in: nova-compute (Juju Charms Collection)
       Status: New => Invalid

** Also affects: nova (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: nova (Ubuntu)
   Importance: Undecided => Medium

** Tags added: icehouse

You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to nova in Ubuntu.

  nova-compute doesn't reconnect to libvirtd

Status in nova package in Ubuntu:
Status in nova-compute package in Juju Charms Collection:

Bug description:
  I've found nova-compute disabled on a prod system with this in the

  2015-01-09 20:14:53.906 26500 WARNING nova.virt.libvirt.driver [-]
  Connection to libvirt lost: 1

  And this in libvirt.log:

  2015-01-09 20:14:53.647+0000: 6646: error : netcfStateCleanup:109 :
  internal error: Attempt to close netcf state driver with open

  However, libvirtd seems to operate normally now. After restarting
  nova-compute it connected successfully to libvirtd.

  Shouldn't nova-compute try reconnect automatically?

To manage notifications about this bug go to:

More information about the Ubuntu-openstack-bugs mailing list