Thanks, I've proposed the package for precise-proposed. In order for the SRU team to accept it, they'll need an explicit test case filled in under '[TEST CASE]' in the bug description. Can someone please fill that in? Is it something like:
virsh start vm1 virsh destroy vm1 & for i in `seq 1 5`; do virsh vncdisplay vm1; done ? ** Description changed: - libvirtError: Timed out during operation: cannot acquire state change + 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] + + + [REGRESSION POTENTIAL] + + This patch is cherrypicked from upstream and has been tested using + openstack. It has so far shown no regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1254872 Title: libvirtError: Timed out during operation: cannot acquire state change lock To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1254872/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
