fixed 1.0.5-3 tag 710517 +pending thanks On Fri, Jun 07, 2013 at 11:02:33PM +0200, Ferenc Wagner wrote: > found 710517 0.9.12-11 > fixed 710517 0.10.0 > tags 710517 + patch > thanks > > "Carpenter, Christopher" <[email protected]> writes: > > > This bug seems to happen every time I try to virsh destroy (or use > > appropriate libvirt API call) while already having an open console via > > virsh console. > > I also hit this issue. It's not 100% reproducible for me, but almost. > In a production cluster hosting virtual machines it leads to cluster > fencing, ie. hard reboot of the affected host machine, as its VMs become > unmanageable when libvirtd dies. So I consider this a serious bug, but > also an easy to fix one: upstream already fixed it as noted in the > upstream tracker (altough an unrelated commit is mentioned there by > mistake; I included the fixed line based on that info, not on testing). > > I wonder why the original report indicated version 0.9.12-11.1, did that > version officially exist? On the other hand, it's actually the version > given to my locally modified package (with the attached patch added to > fix this bug). Anybody interested can get it from: > deb(-src) http://apt.niif.hu/debian wheezy main > > As this bug affects wheezy, I hereby plea for including the fix in a > stable update.
Thanks for digging this up. I've pushed this to the git's wheezy branch for the next point release. Cheers, -- Guido -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
