[Bug 1854710] Re: pthread_rwlock_trywrlock results in hang

Maybe this is another bug, that was fixed in upstream glibc 2.27/master by commit https://github.com/bminor/glibc/commit/f6d0e8c36f02b387d33f2cc58c7cb204f201d92e https://sourceware.org/bugzilla/show_bug.cgi?id=23861, but not in the Ubuntu 18.04? ** Bug watch added: Sourceware.org Bugzilla #23861

[Bug 1854710] [NEW] pthread_rwlock_trywrlock results in hang

Public bug reported: glibc in Bionic has a bug, that was introduced in glibc 2.26 and was fixed in 2.30 by the upstream: https://sourceware.org/bugzilla/show_bug.cgi?id=23844 Tis fix should be backported to the Bionic LTS, because bug causes deadlocks under load in all soft, which uses this

[Bug 1772897] Re: Event-triggered workflows fail on start

This fix should be backported to queens. ** Also affects: mistral (Ubuntu) Importance: Undecided Status: New ** No longer affects: mistral (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1582990] Re: internal error: End of file from monitor

Upstream reverted this fix: https://github.com/libvirt/libvirt/commit/72adaf2f10509c3682f2c65ffad4176e00e5a2fb -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1582990 Title: internal error: End of

[Bug 1647389] Re: Regression: Live migrations can still crash after CVE-2016-5403 fix

This bug DOES NOT fixed in Xenial QEMU package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1647389 Title: Regression: Live migrations can still crash after CVE-2016-5403 fix To manage

[Bug 1612089] Re: Fix for CVE-2016-5403 causes crash on migration if memory stats are enabled

Version of the affected qemu is 1:2.5+dfsg-5ubuntu10.6. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1612089 Title: Fix for CVE-2016-5403 causes crash on migration if memory stats are enabled

[Bug 1612089] Re: Fix for CVE-2016-5403 causes crash on migration if memory stats are enabled

With this series of patches fixing CVE-2016-5403 some live migrations crash with error: 9006: error : qemuProcessReportLogError:1813 : internal error: early end of file from monitor, possible problem: 2016-11-15T12:55:51.353085Z qemu-system-x86_64: VQ 2 size 0x80 < last_avail_idx 0x1 - used_idx

[Bug 1209101] Re: Non-public flavor cannot be used in created tenant

** Also affects: nova (Ubuntu) Importance: Undecided Status: New ** No longer affects: nova (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1209101 Title: Non-public flavor cannot

[Bug 1262641] Re: virsh save and virsh managedsave failed with cpu mode = host-passthrough

I confirm that fix (libvirt 1.2.2-0ubuntu13.1.10) works. The bug is fixed in libvirt from trusty-proposed. Thank you! ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 1312507] Re: rabbitmq-server fails to start on a IPv6-Only environment/epmd is not IPv6 enabled

After upgrading erlang to 1:16.b.3-dfsg-1ubuntu2.1, rabbitmq-server have been broken. Now it can't starts with epdm environment variable like export ERL_EPMD_ADDRESS=10.0.0.1 in /etc/rabbitmq/rabbitmq- env.conf -- You received this bug notification because you are a member of Ubuntu Server

[Bug 1312507] Re: rabbitmq-server fails to start on a IPv6-Only environment/epmd is not IPv6 enabled

After upgrading erlang to 1:16.b.3-dfsg-1ubuntu2.1, rabbitmq-server have been broken. Now it can't starts with epdm environment variable like export ERL_EPMD_ADDRESS=10.0.0.1 in /etc/rabbitmq/rabbitmq- env.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which

[Bug 1262641] Re: virsh save and virsh managedsave failed with cpu mode = host-passthrough

This bug still present in libvirt 1.2.2. And patch has not been discussed upstream. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1262641 Title: virsh save and virsh managedsave failed with cpu

[Bug 1262641] Re: virsh save and virsh managedsave failed with cpu mode = host-passthrough

Unfortunately, in libvirt 1.2.1-0ubuntu4 this bug still exists. And I don't realize how the patch that enables host-passthrough for ARM/AArch64 (not amd64) can fix this bug for other architectures (i386, amd64, powerpc etc). -- You received this bug notification because you are a member of

[Bug 1262641] Re: virsh save and virsh managedsave failed with cpu mode = host-passthrough

There is patch to workaround for this bug, that also fixes similar error after live migration of vm with cpu mode host-passthrough. ** Patch added: dont-fail-without-cpu-model.patch

[Bug 573596] Re: autostart doesn't work

http://code.google.com/p/madwimax/issues/detail?id=48 Solution from the author: http://github.com/ago/madwimax/commit/a6f1d42b26f939f0bea3dedf269d9251b1fb097e ** Bug watch added: code.google.com/p/madwimax/issues #48 http://code.google.com/p/madwimax/issues/detail?id=48 -- autostart doesn't