yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1228977@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package libvirt - 1.1.1-0ubuntu8.7

---------------
libvirt (1.1.1-0ubuntu8.7) saucy-proposed; urgency=medium

  * cherrypick d/p/add-a-mutex-to-serialize-updates-to-firewall from
    upstream to complete the concurrency issue fix (LP: #1228977)

libvirt (1.1.1-0ubuntu8.6) saucy-proposed; urgency=medium

  * Cherrypick upstream patches to fix concurrency race (LP: #1228977)
 -- Serge Hallyn <serge.hallyn@xxxxxxxxxx>   Mon, 10 Mar 2014 11:22:20 -0500

** Changed in: libvirt (Ubuntu Saucy)
       Status: Fix Committed => Fix Released

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

Title:
  n-cpu seems to crash when running with libvirt 1.1.1 from ubuntu cloud
  archive

Status in Ubuntu Cloud Archive:
  Confirmed
Status in OpenStack Compute (Nova):
  Confirmed
Status in “libvirt” package in Ubuntu:
  Fix Released
Status in “libvirt” source package in Saucy:
  Fix Released

Bug description:
  impact
  ------

  any concurrent use of libvirt may lockup libirt

  test case
  ---------

  use libvirt concurrently, specifically in nwfilter + createDomain
  calls. e.g. run devstack-gate against this

  regression potential
  --------------------

  upstream stable branch update - should be low

  We experienced a series of jenkins rejects starting overnight on
  Saturday whose root cause is still not quite tracked down yet.
  However, they all have a couple of things in common:

  1) they are the first attempt to use libvir 1.0.6 from havana cloud archive for ubuntu precise
  2) the fails are all related to guests not spawning correctly
  3) the n-cpu log just stops about 1/2 way through the tempest log, making my suspect that we did something to either lockup or hard crash n-cpu

  After that change went in no devstack/tempest gating project managed
  to merge a change.

  This needs more investigation, but creating this bug to both reverify
  against, as well as track down this issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1228977/+subscriptions