yahoo-eng-team team mailing list archive

[Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>]

** Changed in: nova
       Status: Fix Committed => Fix Released

** Changed in: nova
    Milestone: None => havana-2

-- 
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/1154635

Title:
  Use event based connection failure handling if libvirt is new enough

Status in OpenStack Compute (Nova):
  Fix Released

Bug description:
  This is related to https://code.launchpad.net/bugs/1154473

  This bug pointed out the fact that the reconnect handling used in the
  libvirt driver is fragile and doomed to break again in the future.  To
  quote danpb from https://review.openstack.org/#/c/24323

  "This approach is really doomed to failure in general since libvirt
  can change which error code is raised in a particular scenario at any
  release. This change isn't making life worse though, so I'll ACK it.

  Libvirt >= 0.10.0 has support for triggering a formal event callback
  when a connection is lost. For the future, we should plan to use that
  in preference to this error check hack if we have new enough libvirt.
  "

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