← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1254872] Re: libvirtError: Timed out during operation: cannot acquire state change lock

 

This bug was fixed in the package libvirt - 0.9.8-2ubuntu17.18

---------------
libvirt (0.9.8-2ubuntu17.18) precise-proposed; urgency=medium

  * d/p/ubuntu/qemu-fix-race-between-async-and-query-jobs.patch: fix a race
    between asynchronous and query jobs.  (LP: #1254872)
 -- Serge Hallyn <serge.hallyn@xxxxxxxxxx>   Tue, 11 Mar 2014 14:14:38 -0500

** Changed in: libvirt (Ubuntu Precise)
       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/1254872

Title:
  libvirtError: Timed out during operation: cannot acquire state change
  lock

Status in OpenStack Compute (Nova):
  Triaged
Status in Automated testing of Ubuntu ISO images:
  New
Status in “libvirt” package in Ubuntu:
  Fix Released
Status in “libvirt” source package in Precise:
  Fix Released

Bug description:
  libvirtError: Timed out during operation: cannot acquire state change
  lock

  Source:

  http://logs.openstack.org/72/58372/1/check/check-tempest-devstack-vm-full/4dd1a60/logs/screen-n-cpu.txt.gz
  http://logs.openstack.org/72/58372/1/check/check-tempest-devstack-vm-full/4dd1a60/testr_results.html.gz

  Query: "libvirtError: Timed out during operation: cannot acquire state
  change lock" AND filename:"logs/screen-n-cpu.txt"

  http://logstash.openstack.org/#eyJzZWFyY2giOiJcImxpYnZpcnRFcnJvcjogVGltZWQgb3V0IGR1cmluZyBvcGVyYXRpb246IGNhbm5vdCBhY3F1aXJlIHN0YXRlIGNoYW5nZSBsb2NrXCIgQU5EIGZpbGVuYW1lOlwibG9ncy9zY3JlZW4tbi1jcHUudHh0XCIiLCJmaWVsZHMiOltdLCJvZmZzZXQiOjAsInRpbWVmcmFtZSI6IjYwNDgwMCIsImdyYXBobW9kZSI6ImNvdW50IiwidGltZSI6eyJ1c2VyX2ludGVydmFsIjowfSwic3RhbXAiOjEzODU0MTI3MzA4NzQsIm1vZGUiOiIiLCJhbmFseXplX2ZpZWxkIjoiIn0=

  [IMPACT]

  Queries against a domain which is being worked on asynchronously
  can result in hung clients and the inability to do anything
  further with that domain.

  [TEST CASE]

  Setup openstack cluster with heavy VM turnover and querying.

  [REGRESSION POTENTIAL]

  This patch is cherrypicked from upstream and has been tested using
  openstack.  It has so far shown no regressions.

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