[Bug 1856279] Re: demote vlan to universe in 20.04
** Changed in: cloud-archive Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to vlan in Ubuntu. https://bugs.launchpad.net/bugs/1856279 Title: demote vlan to universe in 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1856279/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1844455] Re: Memory leak of struct _virPCIDeviceAddress on libvirt
This bug was fixed in the package libvirt - 4.0.0-1ubuntu8.15~cloud0 --- libvirt (4.0.0-1ubuntu8.15~cloud0) xenial-queens; urgency=medium . * New update for the Ubuntu Cloud Archive. . libvirt (4.0.0-1ubuntu8.15) bionic; urgency=medium . * d/p/lp-1844455-node_device_conf-Don-t-leak-physical_function.patch: fix memory-leak from PCI-related structure. (LP: #1844455) ** Changed in: cloud-archive/queens Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/1844455 Title: Memory leak of struct _virPCIDeviceAddress on libvirt To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1844455/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1869366] Re: RM: python-tx-tftp package, not needed anymore?
It doesn't appear to be part of the openstack dependency chain so it's not needed by openstack. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to python-tx-tftp in Ubuntu. https://bugs.launchpad.net/bugs/1869366 Title: RM: python-tx-tftp package, not needed anymore? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-tx-tftp/+bug/1869366/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1829823] Re: libvirt-bin: during shutdown libvirt-bin is stopped before libvirt-guests causing hang
I've just released 1.3.1-1ubuntu10.29~cloud0 to mitaka-updates. ** Changed in: cloud-archive/mitaka Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/1829823 Title: libvirt-bin: during shutdown libvirt-bin is stopped before libvirt- guests causing hang To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1829823/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1845321] Re: cinder-daemons autopkgtest must override driver to use pymysql
According to [1], cinder autopkgtests ran successfully for 2:14.0.2-0ubuntu1, therefore I'm going to tag this as verified for disco (autopkgtest fix was provided in version 2:14.0.1-0ubuntu3). [1] http://autopkgtest.ubuntu.com/packages/c/cinder/disco/amd64 http://autopkgtest.ubuntu.com/packages/c/cinder/disco/arm64 http://autopkgtest.ubuntu.com/packages/c/cinder/disco/armhf http://autopkgtest.ubuntu.com/packages/c/cinder/disco/i386 http://autopkgtest.ubuntu.com/packages/c/cinder/disco/ppc64el http://autopkgtest.ubuntu.com/packages/c/cinder/disco/s390x ** Tags added: verification-done-disco -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1845321 Title: cinder-daemons autopkgtest must override driver to use pymysql To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cinder/+bug/1845321/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1770295] Re: ceilometer compute cannot collection memory.usage meter for all vm in one compute node
** Also affects: cloud-archive/queens Importance: Undecided Status: New ** Changed in: cloud-archive/queens Status: New => Incomplete ** Changed in: cloud-archive/queens Importance: Undecided => Low ** Changed in: cloud-archive Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/1770295 Title: ceilometer compute cannot collection memory.usage meter for all vm in one compute node To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1770295/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1856279] Re: demote vlan to universe in 20.04
** Changed in: nova (Ubuntu) Status: New => Triaged ** Changed in: cloud-archive Status: New => Triaged ** Changed in: cloud-archive Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to vlan in Ubuntu. https://bugs.launchpad.net/bugs/1856279 Title: demote vlan to universe in 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1856279/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1845321] Re: cinder-daemons autopkgtest must override driver to use pymysql
@Christian, I've added a card for verification of bug 1838691 to our trello board. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1845321 Title: cinder-daemons autopkgtest must override driver to use pymysql To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cinder/+bug/1845321/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1845321] Re: cinder-daemons autopkgtest must override driver to use pymysql
This is fixed in Disco (Stein) as of cinder 2:14.0.1-0ubuntu3 ** Changed in: cinder (Ubuntu Disco) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1845321 Title: cinder-daemons autopkgtest must override driver to use pymysql To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cinder/+bug/1845321/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1845321] Re: cinder-daemons autopkgtest must override driver to use pymysql
Thanks for checking! Disco fix is in the unapproved queue: https://launchpad.net/ubuntu/disco/+queue?queue_state=1_text=cinder -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1845321 Title: cinder-daemons autopkgtest must override driver to use pymysql To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cinder/+bug/1845321/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1845321] Re: cinder-daemons autopkgtest must override driver to use pymysql
@Christian, thanks for the patch! I'll get that applied and uploaded. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1845321 Title: cinder-daemons autopkgtest must override driver to use pymysql To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cinder/+bug/1845321/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1845321] Re: cinder-daemons autopkgtest must override driver to use pymysql
I've uploaded 2:14.0.1-0ubuntu3 to the disco unapproved queue which includes 2:14.0.1-0ubuntu2 and provides a fix for disco autopkgtest failure. Note that autopkgtests were successfully executed as this was uploaded via https://bileto.ubuntu.com/#/ticket/3813. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1845321 Title: cinder-daemons autopkgtest must override driver to use pymysql To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cinder/+bug/1845321/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1845321] Re: cinder-daemons autopkgtest must override driver to use pymysql
This is also fixed in the latest upload to eoan. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1845321 Title: cinder-daemons autopkgtest must override driver to use pymysql To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cinder/+bug/1845321/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1841277] [NEW] please drop python-swiftclient BD
Public bug reported: In eoan python-swiftclient binary package has been removed. Once simplestreams drops it's BD it should allow python-swiftclient source package to migrate out of eoan-proposed. ** Affects: simplestreams (Ubuntu) Importance: High Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to simplestreams in Ubuntu. https://bugs.launchpad.net/bugs/1841277 Title: please drop python-swiftclient BD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simplestreams/+bug/1841277/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1829380] Update Released
The verification of the Stable Release Update for qemu has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1829380 Title: race condition between vhost_net_stop and CHR_EVENT_CLOSED on shutdown crashes qemu (fix regression) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1829380/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1829380] Re: race condition between vhost_net_stop and CHR_EVENT_CLOSED on shutdown crashes qemu (fix regression)
This bug was fixed in the package qemu - 1:2.5+dfsg-5ubuntu10.40~cloud0 --- qemu (1:2.5+dfsg-5ubuntu10.40~cloud0) trusty-mitaka; urgency=medium . * New update for the Ubuntu Cloud Archive. . qemu (1:2.5+dfsg-5ubuntu10.40) xenial; urgency=medium . * Restore patches that caused regression - d/p/lp1823458/add-VirtIONet-vhost_stopped-flag-to-prevent-multiple.patch - d/p/lp1823458/do-not-call-vhost_net_cleanup-on-running-net-from-ch.patch * Fix regression introduced by above patches (LP: #1829380) - d/p/lp1829380.patch . [ Rafael David Tinoco ] * d/p/lp1828288/target-i386-Set-AMD-alias-bits-after-filtering-CPUID.patch - Fix issues with CPUID_EXT2_AMD_ALIASES allowing guests using cpu passthrough to boot. (LP: #1828288) ** Changed in: cloud-archive/mitaka Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1829380 Title: race condition between vhost_net_stop and CHR_EVENT_CLOSED on shutdown crashes qemu (fix regression) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1829380/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1829380] Please test proposed package
Hello Dan, or anyone else affected, Accepted qemu into mitaka-proposed. The package will build now and be available in the Ubuntu Cloud Archive in a few hours, and then in the -proposed repository. Please help us by testing this new package. To enable the -proposed repository: sudo add-apt-repository cloud-archive:mitaka-proposed sudo apt-get update Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-mitaka-needed to verification-mitaka-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-mitaka-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: cloud-archive/mitaka Status: Triaged => Fix Committed ** Tags added: verification-mitaka-needed -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1829380 Title: race condition between vhost_net_stop and CHR_EVENT_CLOSED on shutdown crashes qemu (fix regression) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1829380/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1829823] Re: libvirt-bin: during shutdown libvirt-bin is stopped before libvirt-guests causing hang
** Also affects: cloud-archive/mitaka Importance: Undecided Status: New ** Changed in: cloud-archive/mitaka Status: New => In Progress ** Changed in: cloud-archive/mitaka Assignee: (unassigned) => Matthew Ruffell (mruffell) ** Changed in: cloud-archive Assignee: Matthew Ruffell (mruffell) => (unassigned) ** Changed in: cloud-archive Status: In Progress => Invalid -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/1829823 Title: libvirt-bin: during shutdown libvirt-bin is stopped before libvirt- guests causing hang To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1829823/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1829380] Re: race condition between vhost_net_stop and CHR_EVENT_CLOSED on shutdown crashes qemu (fix regression)
This bug was fixed in the package qemu - 1:2.8+dfsg-3ubuntu2.9~cloud6 --- qemu (1:2.8+dfsg-3ubuntu2.9~cloud6) xenial-ocata; urgency=medium . * SECURITY UPDATE: Add support for exposing md-clear functionality to guests - d/p/ubuntu/enable-md-clear.patch - CVE-2018-12126, CVE-2018-12127, CVE-2018-12130, CVE-2019-11091 * SECURITY UPDATE: heap overflow when loading device tree blob - d/p/ubuntu/CVE-2018-20815.patch: specify how large the buffer to copy the device tree blob into is. - CVE-2018-20815 * SECURITY UPDATE: information leak in SLiRP - d/p/ubuntu/CVE-2019-9824.patch: check sscanf result when emulating ident. - CVE-2019-9824 * d/p/ubuntu/fix-virtio-net-regression.patch: Fix regression of failing qemu guest networking (LP: #1829380). ** Changed in: cloud-archive/ocata Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1829380 Title: race condition between vhost_net_stop and CHR_EVENT_CLOSED on shutdown crashes qemu (fix regression) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1829380/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1829380] Update Released
The verification of the Stable Release Update for qemu has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-12126 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-12127 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-12130 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-20815 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-11091 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-9824 -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1829380 Title: race condition between vhost_net_stop and CHR_EVENT_CLOSED on shutdown crashes qemu (fix regression) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1829380/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1829380] Please test proposed package
Hello Dan, or anyone else affected, Accepted qemu into ocata-proposed. The package will build now and be available in the Ubuntu Cloud Archive in a few hours, and then in the -proposed repository. Please help us by testing this new package. To enable the -proposed repository: sudo add-apt-repository cloud-archive:ocata-proposed sudo apt-get update Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-ocata-needed to verification-ocata-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-ocata-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: cloud-archive/ocata Status: Triaged => Fix Committed ** Tags added: verification-ocata-needed -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1829380 Title: race condition between vhost_net_stop and CHR_EVENT_CLOSED on shutdown crashes qemu (fix regression) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1829380/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1829380] Re: race condition between vhost_net_stop and CHR_EVENT_CLOSED on shutdown crashes qemu (fix regression)
** Also affects: cloud-archive/mitaka Importance: Undecided Status: New ** Also affects: cloud-archive/ocata Importance: Undecided Status: New ** Changed in: cloud-archive Status: New => Invalid ** Changed in: cloud-archive/ocata Status: New => Triaged ** Changed in: cloud-archive/ocata Importance: Undecided => Medium ** Changed in: cloud-archive/mitaka Status: New => Triaged ** Changed in: cloud-archive/mitaka Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1829380 Title: race condition between vhost_net_stop and CHR_EVENT_CLOSED on shutdown crashes qemu (fix regression) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1829380/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1823458] Re: race condition between vhost_net_stop and CHR_EVENT_CLOSED on shutdown crashes qemu
This bug was fixed in the package qemu - 1:2.8+dfsg-3ubuntu2.9~cloud5.1 --- qemu (1:2.8+dfsg-3ubuntu2.9~cloud5.1) xenial-ocata; urgency=medium . * d/p/lp1823458/add-VirtIONet-vhost_stopped-flag-to-prevent-multiple.patch, d/p/lp1823458/do-not-call-vhost_net_cleanup-on-running-net-from-ch.patch: - Prevent crash due to race condition on shutdown; this is fixed differently upstream (starting in Bionic), but the change is too large to backport into Xenial. These two very small patches work around the problem in an unintrusive way. (LP: #1823458) ** Changed in: cloud-archive/ocata Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1823458 Title: race condition between vhost_net_stop and CHR_EVENT_CLOSED on shutdown crashes qemu To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1823458/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1823458] Re: race condition between vhost_net_stop and CHR_EVENT_CLOSED on shutdown crashes qemu
This bug was fixed in the package qemu - 1:2.5+dfsg-5ubuntu10.37~cloud0 --- qemu (1:2.5+dfsg-5ubuntu10.37~cloud0) trusty-mitaka; urgency=medium . * New update for the Ubuntu Cloud Archive. . qemu (1:2.5+dfsg-5ubuntu10.37) xenial; urgency=medium . * d/p/lp1823458/add-VirtIONet-vhost_stopped-flag-to-prevent-multiple.patch, d/p/lp1823458/do-not-call-vhost_net_cleanup-on-running-net-from-ch.patch: - Prevent crash due to race condition on shutdown; this is fixed differently upstream (starting in Bionic), but the change is too large to backport into Xenial. These two very small patches work around the problem in an unintrusive way. (LP: #1823458) ** Changed in: cloud-archive/mitaka Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1823458 Title: race condition between vhost_net_stop and CHR_EVENT_CLOSED on shutdown crashes qemu To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1823458/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1823458] Update Released
The verification of the Stable Release Update for qemu has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1823458 Title: race condition between vhost_net_stop and CHR_EVENT_CLOSED on shutdown crashes qemu To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1823458/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1823458] Update Released
The verification of the Stable Release Update for qemu has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1823458 Title: race condition between vhost_net_stop and CHR_EVENT_CLOSED on shutdown crashes qemu To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1823458/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1823458] Please test proposed package
Hello Dan, or anyone else affected, Accepted qemu into mitaka-proposed. The package will build now and be available in the Ubuntu Cloud Archive in a few hours, and then in the -proposed repository. Please help us by testing this new package. To enable the -proposed repository: sudo add-apt-repository cloud-archive:mitaka-proposed sudo apt-get update Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-mitaka-needed to verification-mitaka-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-mitaka-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: cloud-archive/mitaka Status: Triaged => Fix Committed ** Tags added: verification-mitaka-needed -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1823458 Title: race condition between vhost_net_stop and CHR_EVENT_CLOSED on shutdown crashes qemu To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1823458/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1823458] Please test proposed package
Hello Dan, or anyone else affected, Accepted qemu into ocata-proposed. The package will build now and be available in the Ubuntu Cloud Archive in a few hours, and then in the -proposed repository. Please help us by testing this new package. To enable the -proposed repository: sudo add-apt-repository cloud-archive:ocata-proposed sudo apt-get update Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-ocata-needed to verification-ocata-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-ocata-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: cloud-archive/ocata Status: Triaged => Fix Committed ** Tags added: verification-ocata-needed -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1823458 Title: race condition between vhost_net_stop and CHR_EVENT_CLOSED on shutdown crashes qemu To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1823458/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1823458] Re: race condition between vhost_net_stop and CHR_EVENT_CLOSED on shutdown crashes qemu
** Also affects: cloud-archive/ocata Importance: Undecided Status: New ** Changed in: cloud-archive/ocata Importance: Undecided => Medium ** Changed in: cloud-archive/ocata Status: New => Triaged ** Changed in: cloud-archive Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1823458 Title: race condition between vhost_net_stop and CHR_EVENT_CLOSED on shutdown crashes qemu To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1823458/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1823458] Re: race condition between vhost_net_stop and CHR_EVENT_CLOSED on shutdown crashes qemu
** Also affects: cloud-archive Importance: Undecided Status: New ** Also affects: cloud-archive/mitaka Importance: Undecided Status: New ** Changed in: cloud-archive/mitaka Importance: Undecided => Medium ** Changed in: cloud-archive/mitaka Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1823458 Title: race condition between vhost_net_stop and CHR_EVENT_CLOSED on shutdown crashes qemu To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1823458/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1818880] Re: Deadlock when detaching network interface
Hello Heitor, or anyone else affected, Accepted qemu into mitaka-proposed. The package will build now and be available in the Ubuntu Cloud Archive in a few hours, and then in the -proposed repository. Please help us by testing this new package. To enable the -proposed repository: sudo add-apt-repository cloud-archive:mitaka-proposed sudo apt-get update Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-mitaka-needed to verification-mitaka-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-mitaka-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags added: verification-mitaka-needed ** Changed in: cloud-archive/mitaka Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1818880 Title: Deadlock when detaching network interface To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1818880/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1818880] Please test proposed package
Hello Heitor, or anyone else affected, Accepted qemu into ocata-proposed. The package will build now and be available in the Ubuntu Cloud Archive in a few hours, and then in the -proposed repository. Please help us by testing this new package. To enable the -proposed repository: sudo add-apt-repository cloud-archive:ocata-proposed sudo apt-get update Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-ocata-needed to verification-ocata-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-ocata-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: cloud-archive/ocata Status: Triaged => Fix Committed ** Tags added: verification-ocata-needed -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1818880 Title: Deadlock when detaching network interface To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1818880/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1818880] Re: Deadlock when detaching network interface
** Changed in: cloud-archive/mitaka Importance: Undecided => High ** Changed in: cloud-archive/mitaka Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1818880 Title: Deadlock when detaching network interface To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1818880/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1818880] Re: Deadlock when detaching network interface
** Changed in: cloud-archive/pike Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1818880 Title: Deadlock when detaching network interface To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1818880/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1818880] Re: Deadlock when detaching network interface
Heiter, please if fixes are needed for ocata or pike can you provide us with patches? We need to be careful not to skip cloud archive releases (ie. if this is fixed in xenial but not the ocata and pike cloud archive). -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1818880 Title: Deadlock when detaching network interface To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1818880/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1818880] Re: Deadlock when detaching network interface
I've just accepted qemu version 1:2.11+dfsg-1ubuntu7.12~cloud0 into queens-proposed however the changelog doesn't mention (LP: #1818880) anywhere. Seeing that bionic is marked as fix released I assume queens can be marked as fix released. ** Changed in: cloud-archive/queens Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1818880 Title: Deadlock when detaching network interface To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1818880/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1818880] Re: Deadlock when detaching network interface
The Stein cloud archive has qemu 1:3.1+dfsg-2ubuntu3~cloud0 which corresponds to the current version in disco, so I'm marking this as fix released for Stein. ** Changed in: cloud-archive/stein Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1818880 Title: Deadlock when detaching network interface To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1818880/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1818880] Re: Deadlock when detaching network interface
We don't have qemu in the rocky cloud archive so this is fixed via bionic. ** Changed in: cloud-archive/rocky Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1818880 Title: Deadlock when detaching network interface To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1818880/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1798184] Re: [SRU] PY3: python3-ldap does not allow bytes for DN/RDN/field names
This is fixed in rocky with keystone version 2:14.0.1-0ubuntu3. ** Changed in: keystone/rocky Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to python-ldappool in Ubuntu. https://bugs.launchpad.net/bugs/1798184 Title: [SRU] PY3: python3-ldap does not allow bytes for DN/RDN/field names To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1798184/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1818880] Re: Deadlock when detaching network interface
** Also affects: cloud-archive/ocata Importance: Undecided Status: New ** Also affects: cloud-archive/pike Importance: Undecided Status: New ** Changed in: cloud-archive/stein Importance: Undecided => High ** Changed in: cloud-archive/stein Status: Confirmed => Triaged ** Changed in: cloud-archive/rocky Importance: Undecided => High ** Changed in: cloud-archive/rocky Status: New => Triaged ** Changed in: cloud-archive/queens Importance: Undecided => High ** Changed in: cloud-archive/queens Status: New => Triaged ** Changed in: cloud-archive/pike Importance: Undecided => High ** Changed in: cloud-archive/pike Status: New => Triaged ** Changed in: cloud-archive/ocata Importance: Undecided => High ** Changed in: cloud-archive/ocata Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1818880 Title: Deadlock when detaching network interface To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1818880/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1798184] Re: [SRU] PY3: python3-ldap does not allow bytes for DN/RDN/field names
** Changed in: cloud-archive/stein Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to python-ldappool in Ubuntu. https://bugs.launchpad.net/bugs/1798184 Title: [SRU] PY3: python3-ldap does not allow bytes for DN/RDN/field names To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1798184/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1798184] Re: [SRU] PY3: python3-ldap does not allow bytes for DN/RDN/field names
This bug was fixed in the package keystone - 2:14.0.1-0ubuntu3~cloud0 --- keystone (2:14.0.1-0ubuntu3~cloud0) bionic-rocky; urgency=medium . * New update for the Ubuntu Cloud Archive. . keystone (2:14.0.1-0ubuntu3) cosmic; urgency=medium . * d/control, d/p/py3-switch-to-using-unicode-text-values.patch: Enable Keystone LDAP Python 3 support. Patch is cherry-picked from https://review.openstack.org/613648 (LP: #1798184). * d/p/ensure-LDAP-searches-use-unicode-attributes.patch: Cherry-picked from https://review.openstack.org/#/c/643670/ to fix LDAP backend searches (LP: #1820333). ** Changed in: cloud-archive/rocky Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to python-ldappool in Ubuntu. https://bugs.launchpad.net/bugs/1798184 Title: [SRU] PY3: python3-ldap does not allow bytes for DN/RDN/field names To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1798184/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1798184] Re: [SRU] PY3: python3-ldap does not allow bytes for DN/RDN/field names
This has been verified successfully on cosmic-proposed and rocky- proposed. I've added testing details to the other bug that is accompanying this fix at: https://bugs.launchpad.net/keystone/+bug/1820333/comments/7 https://bugs.launchpad.net/keystone/+bug/1820333/comments/8 ** Tags removed: verification-needed verification-needed-cosmic ** Tags added: verification-done verification-done-cosmic ** Changed in: keystone/rocky Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to python-ldappool in Ubuntu. https://bugs.launchpad.net/bugs/1798184 Title: [SRU] PY3: python3-ldap does not allow bytes for DN/RDN/field names To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1798184/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1798184] Re: [SRU] PY3: python3-ldap does not allow bytes for DN/RDN/field names
** Changed in: cloud-archive Status: Fix Released => Fix Committed ** Changed in: cloud-archive/rocky Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to python-ldappool in Ubuntu. https://bugs.launchpad.net/bugs/1798184 Title: [SRU] PY3: python3-ldap does not allow bytes for DN/RDN/field names To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1798184/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1798184] Re: [SRU] PY3: python3-ldap does not allow bytes for DN/RDN/field names
Verification on cosmic-proposed failed (See bug in comment #19). I'm working on a fix for that. ** Tags removed: verification-needed verification-needed-cosmic ** Tags added: verification-failed verification-failed-cosmic -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to python-ldappool in Ubuntu. https://bugs.launchpad.net/bugs/1798184 Title: [SRU] PY3: python3-ldap does not allow bytes for DN/RDN/field names To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1798184/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1816170] Re: KVM instances fail at creation with: Failed to get shared "write" lock Is another process using the image?
Targeting qemu for input from that end. ** Also affects: qemu (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1816170 Title: KVM instances fail at creation with: Failed to get shared "write" lock Is another process using the image? To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1816170/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1798184] Re: [SRU] PY3: python3-ldap does not allow bytes for DN/RDN/field names
** Summary changed: - PY3: python3-ldap does not allow bytes for DN/RDN/field names + [SRU] PY3: python3-ldap does not allow bytes for DN/RDN/field names ** Description changed: + [Impact] + Keystone LDAP backend doesn't work for PY3. + Under Python 2, python-ldap uses bytes by default. Under Python 3 this is removed and bytes aren't allowed for DN/RDN/field names. More details are here: http://www.python-ldap.org/en/latest/bytes_mode.html#bytes-mode and here: https://github.com/python-ldap/python-ldap/blob/python-ldap-3.1.0/Lib/ldap/ldapobject.py#L111 == initial traceback == Here's the initial traceback from the failure: https://paste.ubuntu.com/p/67THZb2m5m/ The last bit of the error is: - File "/usr/lib/python3/dist-packages/ldap/ldapobject.py", line 314, in _ldap_call - result = func(*args,**kwargs) + File "/usr/lib/python3/dist-packages/ldap/ldapobject.py", line 314, in _ldap_call + result = func(*args,**kwargs) TypeError: simple_bind() argument 1 must be str or None, not bytes A closer look at func shows: func= args=(b'cn=admin,dc=test,dc=com', b'crapper', None, None) == keystone ldap backend use of python-ldap == In simple_bind_s() of keystone's ldap backend, who and cred are encoded as byte strings: https://github.com/openstack/keystone/blob/14.0.0/keystone/identity/backends/ldap/common.py#L885 but that appears to no longer be valid use of python-ldap for py3. + + + [Test Case] + + Run charm-keystone-ldap functional tests for OpenStack Rocky or above. + + [Regression Potential] + The only regression potential would be for PY2 code paths. PY3 code paths never worked for keystone's LDAP backend. The approach to the patch have purposefully minimized amount of code required and therefore regression potential for PY2. Note that Rocky for Ubuntu supports PY2 but as of Stein Ubuntu has dropped PY2 support. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to python-ldappool in Ubuntu. https://bugs.launchpad.net/bugs/1798184 Title: [SRU] PY3: python3-ldap does not allow bytes for DN/RDN/field names To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1798184/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1798184] Re: PY3: python3-ldap does not allow bytes for DN/RDN/field names
** Changed in: python-ldappool (Ubuntu Disco) Status: Triaged => Fix Released ** Changed in: keystone (Ubuntu Disco) Status: Triaged => Fix Released ** Changed in: cloud-archive/stein Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to python-ldappool in Ubuntu. https://bugs.launchpad.net/bugs/1798184 Title: PY3: python3-ldap does not allow bytes for DN/RDN/field names To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1798184/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1108935] Re: [MIR] websockify, spice-html5
This is fixed for nova in 2:19.0.0~b1~git2019013113.33aad0fe41-0ubuntu2. ** Changed in: nova (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to websockify in Ubuntu. https://bugs.launchpad.net/bugs/1108935 Title: [MIR] websockify, spice-html5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1108935/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1108935] Re: [MIR] websockify, spice-html5
** Also affects: nova (Ubuntu) Importance: Undecided Status: New ** Changed in: nova (Ubuntu) Status: New => Triaged ** Changed in: nova (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to websockify in Ubuntu. https://bugs.launchpad.net/bugs/1108935 Title: [MIR] websockify, spice-html5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1108935/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1798184] Re: PY3: python3-ldap does not allow bytes for DN/RDN/field names
Marked as fix released for upstream ldappool as this is fixed in 2.3.1 ** Also affects: keystone (Ubuntu) Importance: Undecided Status: New ** Also affects: keystone (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: keystone (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: keystone (Ubuntu Cosmic) Status: New => Triaged ** Changed in: keystone (Ubuntu Cosmic) Importance: Undecided => High ** Changed in: keystone (Ubuntu Disco) Status: New => Triaged ** Changed in: keystone (Ubuntu Disco) Importance: Undecided => High ** Also affects: cloud-archive Importance: Undecided Status: New ** Also affects: cloud-archive/rocky Importance: Undecided Status: New ** Also affects: cloud-archive/stein Importance: Undecided Status: New ** Changed in: cloud-archive/rocky Status: New => Triaged ** Changed in: cloud-archive/stein Status: New => Triaged ** Changed in: cloud-archive/rocky Importance: Undecided => High ** Changed in: cloud-archive/stein Importance: Undecided => High ** Also affects: python-ldappool (Ubuntu) Importance: Undecided Status: New ** Changed in: python-ldappool (Ubuntu Cosmic) Importance: Undecided => High ** Changed in: python-ldappool (Ubuntu Cosmic) Status: New => Triaged ** Changed in: python-ldappool (Ubuntu Disco) Importance: Undecided => High ** Changed in: python-ldappool (Ubuntu Disco) Status: New => Triaged ** Changed in: ldappool Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to python-ldappool in Ubuntu. https://bugs.launchpad.net/bugs/1798184 Title: PY3: python3-ldap does not allow bytes for DN/RDN/field names To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1798184/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1808773] Re: python-boto: libssl1.1 dependency problems
Ok no problem, and thank you for responding back with details. ** Changed in: python-boto (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to python-boto in Ubuntu. https://bugs.launchpad.net/bugs/1808773 Title: python-boto: libssl1.1 dependency problems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-boto/+bug/1808773/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1808773] Re: python-boto: libssl1.1 dependency problems
Architectures trimmed for formatting: $ rmadison libssl1.1 libssl1.1 | 1.1.0g-2ubuntu4 | bionic libssl1.1 | 1.1.0g-2ubuntu4.3 | bionic-security libssl1.1 | 1.1.0g-2ubuntu4.3 | bionic-updates libssl1.1 | 1.1.1-1ubuntu2 | cosmic libssl1.1 | 1.1.1-1ubuntu2.1 | cosmic-security libssl1.1 | 1.1.1-1ubuntu2.1 | cosmic-updates libssl1.1 | 1.1.1a-1ubuntu2 | disco -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to python-boto in Ubuntu. https://bugs.launchpad.net/bugs/1808773 Title: python-boto: libssl1.1 dependency problems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-boto/+bug/1808773/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1808773] Re: python-boto: libssl1.1 dependency problems
I'm not sure where libssl1.1 version 1.1.1a-2+ubuntu18.04.1+deb.sury.org+1 is coming from. Where are you getting libssl1.1 from? What does 'apt policy libssl1.1' show? Here are the current versios in bionic+ Ubuntu archives: $ rmadison libssl1.1 libssl1.1 | 1.1.0g-2ubuntu4 | bionic | amd64, arm64, armhf, i386, ppc64el, s390x libssl1.1 | 1.1.0g-2ubuntu4.3 | bionic-security | amd64, arm64, armhf, i386, ppc64el, s390x libssl1.1 | 1.1.0g-2ubuntu4.3 | bionic-updates | amd64, arm64, armhf, i386, ppc64el, s390x libssl1.1 | 1.1.1-1ubuntu2| cosmic | amd64, arm64, armhf, i386, ppc64el, s390x libssl1.1 | 1.1.1-1ubuntu2.1 | cosmic-security | amd64, arm64, armhf, i386, ppc64el, s390x libssl1.1 | 1.1.1-1ubuntu2.1 | cosmic-updates | amd64, arm64, armhf, i386, ppc64el, s390x libssl1.1 | 1.1.1a-1ubuntu2 | disco | amd64, arm64, armhf, i386, ppc64el, s390x -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to python-boto in Ubuntu. https://bugs.launchpad.net/bugs/1808773 Title: python-boto: libssl1.1 dependency problems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-boto/+bug/1808773/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1808773] Re: python-boto: libssl1.1 dependency problems
Hi tomtom, Thanks for reporting this and making Ubuntu better. I was able to install python-boto 2.44.0-1ubuntu2 successfully with apt. Is this still a problem if you use apt to install from the bionic archive? Thanks, Corey ** Changed in: python-boto (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to python-boto in Ubuntu. https://bugs.launchpad.net/bugs/1808773 Title: python-boto: libssl1.1 dependency problems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-boto/+bug/1808773/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1674481] Re: memory overhead of qemu-kvm with ceph rbd and ram-allocation-ratio=0.9 leads to memory starvation
** Changed in: qemu (Ubuntu) Status: Expired => New ** Changed in: ceph (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1674481 Title: memory overhead of qemu-kvm with ceph rbd and ram-allocation-ratio=0.9 leads to memory starvation To manage notifications about this bug go to: https://bugs.launchpad.net/charm-nova-cloud-controller/+bug/1674481/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1789045] Re: keepalived 1:1.2.24-1ubuntu0.16.04.1 breaks Neutron stable branches
Hi again Slawek, Just for some further details, the new versions of keepalived came about due to: https://bugs.launchpad.net/cloud-archive/+bug/1744062. In particular, see https://bugs.launchpad.net/cloud-archive/+bug/1744062/comments/14 for the descriptions of the commits that are included to fix that bug - essentially the fixes cleanup unused ip addresses on startup. The same fixes are in the bionic version of keepalived. Thanks, Corey -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to keepalived in Ubuntu. https://bugs.launchpad.net/bugs/1789045 Title: keepalived 1:1.2.24-1ubuntu0.16.04.1 breaks Neutron stable branches To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1789045/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1789045] Re: keepalived 1:1.2.24-1ubuntu0.16.04.1 breaks Neutron stable branches
Slawek, Thank you for reporting this issue. The new keepalived versions include a cherry-pick of https://github.com/acassen/keepalived/commit/e90a633c34fbe6ebbb891aa98bf29ce579b8b45c. I'm currently building a new xenial version of keepalived in a PPA for testing purposes with this patch removed. Would you be able to re-run tests with it to see if this fixes the issue? You can get the fix by running the following commands on a xenial machine. You'll need to use mitaka (base xenial without cloud archive) or use the ocata or pike cloud archives. sudo add-apt-repository ppa:corey.bryant/xenial-bug-1789045 sudo apt update -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to keepalived in Ubuntu. https://bugs.launchpad.net/bugs/1789045 Title: keepalived 1:1.2.24-1ubuntu0.16.04.1 breaks Neutron stable branches To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1789045/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1789045] Re: keepalived 1:1.2.24-1ubuntu0.16.04.1 breaks Neutron stable branches
Slawek, for stable/queens, can you confirm the version of keepalived that your tests are running with? The queens cloud archive has keepalived 1:1.3.9-1ubuntu0.18.04.1~cloud0, however I'm wondering if you're running with the base xenial version of 1:1.2.24-1ubuntu0.16.04.1. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to keepalived in Ubuntu. https://bugs.launchpad.net/bugs/1789045 Title: keepalived 1:1.2.24-1ubuntu0.16.04.1 breaks Neutron stable branches To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1789045/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1744062] Re: [SRU] L3 HA: multiple agents are active at the same time
This bug was fixed in the package keepalived - 1:1.3.9-1ubuntu0.18.04.1~cloud0 --- keepalived (1:1.3.9-1ubuntu0.18.04.1~cloud0) xenial-queens; urgency=medium . * New update for the Ubuntu Cloud Archive. . keepalived (1:1.3.9-1ubuntu0.18.04.1) bionic; urgency=medium . * d/p/fix-removing-left-over-addresses-if-keepalived-abort.patch: Cherry-picked from upstream to ensure left-over VIPs and eVIPs are properly removed on restart if keepalived terminates abonormally. This fix is from the upstream 1.4.0 release (LP: #1744062). ** Changed in: cloud-archive/queens Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to keepalived in Ubuntu. https://bugs.launchpad.net/bugs/1744062 Title: [SRU] L3 HA: multiple agents are active at the same time To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1744062/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1744062] Update Released
The verification of the Stable Release Update for keepalived has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to keepalived in Ubuntu. https://bugs.launchpad.net/bugs/1744062 Title: [SRU] L3 HA: multiple agents are active at the same time To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1744062/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1744062] Update Released
The verification of the Stable Release Update for keepalived has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to keepalived in Ubuntu. https://bugs.launchpad.net/bugs/1744062 Title: [SRU] L3 HA: multiple agents are active at the same time To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1744062/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1744062] Re: [SRU] L3 HA: multiple agents are active at the same time
This bug was fixed in the package keepalived - 1:1.2.24-1ubuntu0.16.04.1~cloud0 --- keepalived (1:1.2.24-1ubuntu0.16.04.1~cloud0) trusty-mitaka; urgency=medium . * New upstream release for the Ubuntu Cloud Archive. . keepalived (1:1.2.24-1ubuntu0.16.04.1) xenial; urgency=medium . * New upstream version for Ubuntu 16.04 (LP: #1783583). * d/p/fix_message_truncation_with_large_pagesizes.patch: Rebased. * d/p/fix-removing-left-over-addresses-if-keepalived-abort.patch: Cherry-picked from upstream to ensure left-over VIPs and eVIPs are properly removed on restart if keepalived terminates abonormally. This fix is from the upstream 1.4.0 release (LP: #1744062). . keepalived (1:1.2.24-1) unstable; urgency=medium . * [d378a6f] New upstream version 1.2.24 . keepalived (1:1.2.23-1) unstable; urgency=medium . * [94beb84] Imported Upstream version 1.2.23 (Closes: #821941) - fix some segfaults (Closes: #830955) . keepalived (1:1.2.20-1) unstable; urgency=medium . * [2a22d69] Imported Upstream version 1.2.20 enable support for: - nfnetlink - ipset - iptc - snmp rfcv2 and rfcv3 ** Changed in: cloud-archive/mitaka Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to keepalived in Ubuntu. https://bugs.launchpad.net/bugs/1744062 Title: [SRU] L3 HA: multiple agents are active at the same time To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1744062/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1783583] Re: [SRU] keepalived v1.2.24
This bug was fixed in the package keepalived - 1:1.2.24-1ubuntu0.16.04.1~cloud0 --- keepalived (1:1.2.24-1ubuntu0.16.04.1~cloud0) trusty-mitaka; urgency=medium . * New upstream release for the Ubuntu Cloud Archive. . keepalived (1:1.2.24-1ubuntu0.16.04.1) xenial; urgency=medium . * New upstream version for Ubuntu 16.04 (LP: #1783583). * d/p/fix_message_truncation_with_large_pagesizes.patch: Rebased. * d/p/fix-removing-left-over-addresses-if-keepalived-abort.patch: Cherry-picked from upstream to ensure left-over VIPs and eVIPs are properly removed on restart if keepalived terminates abonormally. This fix is from the upstream 1.4.0 release (LP: #1744062). . keepalived (1:1.2.24-1) unstable; urgency=medium . * [d378a6f] New upstream version 1.2.24 . keepalived (1:1.2.23-1) unstable; urgency=medium . * [94beb84] Imported Upstream version 1.2.23 (Closes: #821941) - fix some segfaults (Closes: #830955) . keepalived (1:1.2.20-1) unstable; urgency=medium . * [2a22d69] Imported Upstream version 1.2.20 enable support for: - nfnetlink - ipset - iptc - snmp rfcv2 and rfcv3 ** Changed in: cloud-archive/mitaka Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to keepalived in Ubuntu. https://bugs.launchpad.net/bugs/1783583 Title: [SRU] keepalived v1.2.24 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1783583/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1783583] Update Released
The verification of the Stable Release Update for keepalived has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to keepalived in Ubuntu. https://bugs.launchpad.net/bugs/1783583 Title: [SRU] keepalived v1.2.24 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1783583/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1744062] Please test proposed package
Hello Corey, or anyone else affected, Accepted keepalived into mitaka-proposed. The package will build now and be available in the Ubuntu Cloud Archive in a few hours, and then in the -proposed repository. Please help us by testing this new package. To enable the -proposed repository: sudo add-apt-repository cloud-archive:mitaka-proposed sudo apt-get update Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-mitaka-needed to verification-mitaka-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-mitaka-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: cloud-archive/mitaka Status: Triaged => Fix Committed ** Tags added: verification-mitaka-needed -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to keepalived in Ubuntu. https://bugs.launchpad.net/bugs/1744062 Title: [SRU] L3 HA: multiple agents are active at the same time To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1744062/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1783583] Re: [SRU] keepalived v1.2.24
Hello Corey, or anyone else affected, Accepted keepalived into mitaka-proposed. The package will build now and be available in the Ubuntu Cloud Archive in a few hours, and then in the -proposed repository. Please help us by testing this new package. To enable the -proposed repository: sudo add-apt-repository cloud-archive:mitaka-proposed sudo apt-get update Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-mitaka-needed to verification-mitaka-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-mitaka-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Also affects: cloud-archive Importance: Undecided Status: New ** Also affects: cloud-archive/mitaka Importance: Undecided Status: New ** Changed in: cloud-archive Status: New => Invalid ** Changed in: cloud-archive/mitaka Status: New => Triaged ** Changed in: cloud-archive/mitaka Importance: Undecided => High ** Changed in: cloud-archive/mitaka Status: Triaged => Fix Committed ** Tags added: verification-mitaka-needed -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to keepalived in Ubuntu. https://bugs.launchpad.net/bugs/1783583 Title: [SRU] keepalived v1.2.24 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1783583/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1744062] Re: [SRU] L3 HA: multiple agents are active at the same time
I've just asked for a review in #ubuntu-release. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to keepalived in Ubuntu. https://bugs.launchpad.net/bugs/1744062 Title: [SRU] L3 HA: multiple agents are active at the same time To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1744062/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1744062] Re: [SRU] L3 HA: multiple agents are active at the same time
I've uploaded keepalived 1:1.2.24-1ubuntu0.16.04.1 to the xenial review queue where it is awaiting SRU team review. This xenial fix is paired with https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1783583. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to keepalived in Ubuntu. https://bugs.launchpad.net/bugs/1744062 Title: [SRU] L3 HA: multiple agents are active at the same time To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1744062/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1783583] Re: [SRU] keepalived v1.2.24
I've uploaded keepalived 1:1.2.24-1ubuntu0.16.04.1 to the xenial review queue where it is awaiting SRU team review. ** Also affects: keepalived (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: keepalived (Ubuntu) Status: New => Invalid ** Changed in: keepalived (Ubuntu Xenial) Status: New => Triaged ** Changed in: keepalived (Ubuntu Xenial) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to keepalived in Ubuntu. https://bugs.launchpad.net/bugs/1783583 Title: [SRU] keepalived v1.2.24 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1783583/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1744062] Re: [SRU] L3 HA: multiple agents are active at the same time
** No longer affects: cloud-archive/pike ** No longer affects: cloud-archive/ocata -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to keepalived in Ubuntu. https://bugs.launchpad.net/bugs/1744062 Title: [SRU] L3 HA: multiple agents are active at the same time To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1744062/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1783583] [NEW] [SRU] keepalived v1.2.24
Public bug reported: [Impact] This release sports mostly bug-fixes and we would like to make sure all of our supported customers have access to these improvements. [Test Case] The following SRU process was followed: https://wiki.ubuntu.com/OpenStackUpdates In order to avoid regression of existing consumers, the OpenStack team will run their continuous integration test against the packages that are in -proposed. A successful run of all available tests will be required before the proposed packages can be let into -updates. The OpenStack team will be in charge of attaching the output summary of the executed tests. The OpenStack team members will not mark ‘verification-done’ until this has happened. This SRU will also get/require additional testing alongside https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1744062. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned tests are attached to this bug. [Discussion] ** Affects: keepalived (Ubuntu) Importance: Undecided Status: New ** Description changed: [Impact] - This release sports mostly bug-fixes and we would like to make sure all of our - supported customers have access to these improvements. + This release sports mostly bug-fixes and we would like to make sure all of our supported customers have access to these improvements. [Test Case] The following SRU process was followed: https://wiki.ubuntu.com/OpenStackUpdates - In order to avoid regression of existing consumers, the OpenStack team will - run their continuous integration test against the packages that are in - -proposed. A successful run of all available tests will be required before the - proposed packages can be let into -updates. + In order to avoid regression of existing consumers, the OpenStack team + will run their continuous integration test against the packages that are + in -proposed. A successful run of all available tests will be required + before the proposed packages can be let into -updates. - The OpenStack team will be in charge of attaching the output summary of the - executed tests. The OpenStack team members will not mark ‘verification-done’ until - this has happened. + The OpenStack team will be in charge of attaching the output summary of + the executed tests. The OpenStack team members will not mark + ‘verification-done’ until this has happened. This SRU will also get/require additional testing alongside https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1744062. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned tests are attached to this bug. [Discussion] -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to keepalived in Ubuntu. https://bugs.launchpad.net/bugs/1783583 Title: [SRU] keepalived v1.2.24 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1783583/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1744062] Re: [SRU] L3 HA: multiple agents are active at the same time
I've deleted the keepalived versions from ocata-staging and pike- staging. We should be able to fix this in xenial with a new stable point release and patch backport. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to keepalived in Ubuntu. https://bugs.launchpad.net/bugs/1744062 Title: [SRU] L3 HA: multiple agents are active at the same time To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1744062/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1744062] Please test proposed package
Hello Corey, or anyone else affected, Accepted keepalived into queens-proposed. The package will build now and be available in the Ubuntu Cloud Archive in a few hours, and then in the -proposed repository. Please help us by testing this new package. To enable the -proposed repository: sudo add-apt-repository cloud-archive:queens-proposed sudo apt-get update Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-queens-needed to verification-queens-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-queens-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: cloud-archive/queens Status: Triaged => Fix Committed ** Tags added: verification-queens-needed -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to keepalived in Ubuntu. https://bugs.launchpad.net/bugs/1744062 Title: [SRU] L3 HA: multiple agents are active at the same time To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1744062/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1744062] Re: [SRU] L3 HA: multiple agents are active at the same time
I've uploaded new versions of keepalived to cosmic, bionic (awaiting SRU team review), pike-staging, and ocata-staging. I need to confirm with other cloud archive admins that this is ok to backport to pike/ocata cloud archives prior to promoting to pike-proposed/ocata-proposed. In the mean time if you'd like to test the ocata fix (where this was initially reported) you can install from the staging PPA: sudo add-apt-repository ppa:ubuntu-cloud-archive/ocata-staging sudo apt update And from pike: sudo add-apt-repository ppa:ubuntu-cloud-archive/pike-staging sudo apt update -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to keepalived in Ubuntu. https://bugs.launchpad.net/bugs/1744062 Title: [SRU] L3 HA: multiple agents are active at the same time To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1744062/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1744062] Re: [SRU] L3 HA: multiple agents are active at the same time
Moving back to New for neutron for the time being since we think this may be fixed in keepalived. ** Description changed: + [Impact] + This is the same issue reported in https://bugs.launchpad.net/neutron/+bug/1731595, however that is marked as 'Fix Released' and the issue is still occurring and I can't change back to 'New' so it seems best to just open a new bug. It seems as if this bug surfaces due to load issues. While the fix - provided by Venkata (https://review.openstack.org/#/c/522641/) should - help clean things up at the time of l3 agent restart, issues seem to - come back later down the line in some circumstances. xavpaice mentioned - he saw multiple routers active at the same time when they had 464 - routers configured on 3 neutron gateway hosts using L3HA, and each - router was scheduled to all 3 hosts. However, jhebden mentions that - things seem stable at the 400 L3HA router mark, and it's worth noting - this is the same deployment that xavpaice was referring to. + provided by Venkata in https://bugs.launchpad.net/neutron/+bug/1731595 + (https://review.openstack.org/#/c/522641/) should help clean things up + at the time of l3 agent restart, issues seem to come back later down the + line in some circumstances. xavpaice mentioned he saw multiple routers + active at the same time when they had 464 routers configured on 3 + neutron gateway hosts using L3HA, and each router was scheduled to all 3 + hosts. However, jhebden mentions that things seem stable at the 400 L3HA + router mark, and it's worth noting this is the same deployment that + xavpaice was referring to. - It seems to me that something is being pushed to it's limit, and - possibly once that limit is hit, master router advertisements aren't - being received, causing a new master to be elected. If this is the case - it would be great to get to the bottom of what resource is getting - constrained. + keepalived has a patch upstream in 1.4.0 that provides a fix for + removing left-over addresses if keepalived aborts. That patch will be + cherry-picked to Ubuntu keepalived packages. + + [Test Case] + The following SRU process will be followed: + https://wiki.ubuntu.com/OpenStackUpdates + + In order to avoid regression of existing consumers, the OpenStack team + will run their continuous integration test against the packages that are + in -proposed. A successful run of all available tests will be required + before the proposed packages can be let into -updates. + + The OpenStack team will be in charge of attaching the output summary of + the executed tests. The OpenStack team members will not mark + ‘verification-done’ until this has happened. + + [Regression Potential] + The regression potential is lowered as the fix is cherry-picked without change from upstream. In order to mitigate the regression potential, the results of the aforementioned tests are attached to this bug. + + [Discussion] ** Changed in: neutron (Ubuntu) Status: Triaged => New ** Changed in: neutron (Ubuntu) Importance: High => Undecided ** Changed in: neutron (Ubuntu Xenial) Importance: High => Undecided ** Changed in: neutron (Ubuntu Xenial) Status: Triaged => New ** Changed in: neutron (Ubuntu Bionic) Importance: High => Undecided ** Changed in: neutron (Ubuntu Bionic) Status: Triaged => New -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to keepalived in Ubuntu. https://bugs.launchpad.net/bugs/1744062 Title: [SRU] L3 HA: multiple agents are active at the same time To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1744062/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1744062] Re: [SRU] L3 HA: multiple agents are active at the same time
** Summary changed: - L3 HA: multiple agents are active at the same time + [SRU] L3 HA: multiple agents are active at the same time -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to keepalived in Ubuntu. https://bugs.launchpad.net/bugs/1744062 Title: [SRU] L3 HA: multiple agents are active at the same time To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1744062/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1744062] Re: L3 HA: multiple agents are active at the same time
It appears the following commits are required to fix this for keepalived: commit e90a633c34fbe6ebbb891aa98bf29ce579b8b45c Author: Quentin Armitage Date: Fri Dec 15 21:14:24 2017 + Fix removing left-over addresses if keepalived aborts Issue #718 reported that if keepalived terminates abnormally when it has vrrp instances in master state, it doesn't remove the left-over VIPs and eVIPs when it restarts. This is despite commit f4c10426c saying that it resolved this problem. It turns out that commit f4c10426c did resolve the problem for VIPs or eVIPs, although it did resolve the issue for iptables and ipset configuration. This commit now really resolves the problem, and residual VIPs and eVIPs are removed at startup. Signed-off-by: Quentin Armitage commit f4c10426ca0a7c3392422c22079f1b71e7d4ebe9 Author: Quentin Armitage Date: Sun Mar 6 09:53:27 2016 + Remove ip addresses left over from previous failure If keepalived terminates unexpectedly, for any instances for which it was master, it leaves ip addresses configured on the interfaces. When keepalived restarts, if it starts in backup mode, the addresses must be removed. In addition, any iptables/ipsets entries added for !accept_mode must also be removed, in order to avoid multiple entries being created in iptables. This commit removes any addresses and iptables/ipsets configuration for any interfaces that exist when iptables starts up. If keepalived shut down cleanly, that will only be for non-vmac interfaces, but if it terminated unexpectedly, it can also be for any left-over vmacs. Signed-off-by: Quentin Armitage f4c10426ca0a7c3392422c22079f1b71e7d4ebe9 is already included in: * keepalived 1:1.3.9-1build1 (bionic/queens, cosmic/rocky) * keepalived 1:1.3.2-1build1 (artful/pike) * keepalived 1:1.3.2-1 (zesty/ocata) [1] [1] zesty is EOL - https://launchpad.net/ubuntu/+source/keepalived/1:1.3.2-1 f4c10426ca0a7c3392422c22079f1b71e7d4ebe9 is not included in: * keepalived 1:1.2.19-1ubuntu0.2 (xenial/mitaka) The backport of f4c10426ca0a7c3392422c22079f1b71e7d4ebe9 to xenial does not look trivial. I'd prefer to backport keepalived 1:1.3.2-* to the pike/ocata cloud archives. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to keepalived in Ubuntu. https://bugs.launchpad.net/bugs/1744062 Title: L3 HA: multiple agents are active at the same time To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1744062/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1744062] Re: L3 HA: multiple agents are active at the same time
As reported by Xav in https://bugs.launchpad.net/ubuntu/+bug/1731595: "Comment for the folks that are noticing this as 'fix released' but still affected - see https://github.com/acassen/keepalived/commit/e90a633c34fbe6ebbb891aa98bf29ce579b8b45c for the rest of this fix, we need keepalived to be at least 1.4.0 in order to have this commit." I just checked and the patch Xav referenced can be backported fairly cleanly to at least keepalived 1:1.2.19-1 (xenial/mitaka) and above. ** Also affects: keepalived (Ubuntu) Importance: Undecided Status: New ** No longer affects: keepalived (Ubuntu Artful) ** Changed in: keepalived (Ubuntu) Importance: Undecided => High ** Changed in: keepalived (Ubuntu) Status: New => Triaged ** Changed in: keepalived (Ubuntu Xenial) Importance: Undecided => High ** Changed in: keepalived (Ubuntu Xenial) Status: New => Triaged ** Changed in: keepalived (Ubuntu Bionic) Importance: Undecided => High ** Changed in: keepalived (Ubuntu Bionic) Status: New => Triaged ** No longer affects: cloud-archive/newton ** No longer affects: neutron (Ubuntu Artful) -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to keepalived in Ubuntu. https://bugs.launchpad.net/bugs/1744062 Title: L3 HA: multiple agents are active at the same time To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1744062/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1731595] Re: L3 HA: multiple agents are active at the same time
Since this bug is already marked as fix released for the cloud-archive, let's please track this issue in the following bug: https://bugs.launchpad.net/ubuntu/+bug/1744062 ** No longer affects: keepalived (Ubuntu) ** No longer affects: keepalived (Ubuntu Xenial) ** No longer affects: keepalived (Ubuntu Bionic) -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to keepalived in Ubuntu. https://bugs.launchpad.net/bugs/1731595 Title: L3 HA: multiple agents are active at the same time To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1731595/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1731595] Re: L3 HA: multiple agents are active at the same time
Xav, I just checked and the patch you referenced can be backported fairly cleanly to at least keepalived 1:1.2.19-1 (xenial/mitaka) and above. ** Changed in: keepalived (Ubuntu Xenial) Importance: Undecided => Critical ** Changed in: keepalived (Ubuntu Xenial) Status: New => Triaged ** Changed in: keepalived (Ubuntu Bionic) Importance: Undecided => High ** Changed in: keepalived (Ubuntu Bionic) Status: New => Triaged ** Changed in: keepalived (Ubuntu) Status: New => Triaged ** Changed in: keepalived (Ubuntu) Importance: Undecided => High ** Changed in: keepalived (Ubuntu Xenial) Importance: Critical => High -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to keepalived in Ubuntu. https://bugs.launchpad.net/bugs/1731595 Title: L3 HA: multiple agents are active at the same time To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1731595/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1731595] Re: L3 HA: multiple agents are active at the same time
** No longer affects: keepalived (Ubuntu Zesty) -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to keepalived in Ubuntu. https://bugs.launchpad.net/bugs/1731595 Title: L3 HA: multiple agents are active at the same time To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1731595/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1731595] Re: L3 HA: multiple agents are active at the same time
** Also affects: keepalived (Ubuntu) Importance: Undecided Status: New ** No longer affects: keepalived (Ubuntu Artful) -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to keepalived in Ubuntu. https://bugs.launchpad.net/bugs/1731595 Title: L3 HA: multiple agents are active at the same time To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1731595/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1779162] Update Released
The verification of the Stable Release Update for qemu has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1779162 Title: qemu versions 2.10 and 2.11 have error during migration of larger guests To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1779162/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1779162] Re: qemu versions 2.10 and 2.11 have error during migration of larger guests
This bug was fixed in the package qemu - 1:2.10+dfsg-0ubuntu3.8~cloud1 --- qemu (1:2.10+dfsg-0ubuntu3.8~cloud1) xenial-pike; urgency=medium . * d/p/s390x-fix-storage-attrs-migration-for-non-small-guests.patch: Backported from upstream 2.11.1 release to enable successful migration of non-small guests (LP: #1779162). ** Changed in: cloud-archive/pike Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1779162 Title: qemu versions 2.10 and 2.11 have error during migration of larger guests To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1779162/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1779162] Re: qemu versions 2.10 and 2.11 have error during migration of larger guests
Thanks for testing. Tagging verification-pike-done according to comment #4 results. ** Tags added: verification-pike-done -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1779162 Title: qemu versions 2.10 and 2.11 have error during migration of larger guests To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1779162/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1779162] Please test proposed package
Hello bugproxy, or anyone else affected, Accepted qemu into pike-proposed. The package will build now and be available in the Ubuntu Cloud Archive in a few hours, and then in the -proposed repository. Please help us by testing this new package. To enable the -proposed repository: sudo add-apt-repository cloud-archive:pike-proposed sudo apt-get update Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-pike-needed to verification-pike-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-pike-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: cloud-archive/pike Status: Triaged => Fix Committed ** Tags added: verification-pike-needed -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1779162 Title: qemu versions 2.10 and 2.11 have error during migration of larger guests To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1779162/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1779162] Re: qemu versions 2.10 and 2.11 have error during migration of larger guests
Hello Christian and Frank, Thanks for reporting this and making Ubuntu better. Very much appreciate your details bug description as well. I'm working on backporting this to Pike and will update the bug with more details soon. Thanks, Corey ** Changed in: cloud-archive Status: New => Triaged ** Also affects: cloud-archive/pike Importance: Undecided Status: New ** Changed in: cloud-archive/pike Status: New => Triaged ** Changed in: cloud-archive/pike Importance: Undecided => Critical ** Changed in: cloud-archive Status: Triaged => Invalid ** Changed in: cloud-archive/pike Assignee: (unassigned) => Corey Bryant (corey.bryant) ** Changed in: cloud-archive Assignee: Corey Bryant (corey.bryant) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1779162 Title: qemu versions 2.10 and 2.11 have error during migration of larger guests To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1779162/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1420017] Re: [MIR] python-nosehtmloutput
This would be a Build-Depend and no longer needed. Thanks. ** Changed in: python-nosehtmloutput (Ubuntu) Status: Fix Committed => Invalid -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to python-nosehtmloutput in Ubuntu. https://bugs.launchpad.net/bugs/1420017 Title: [MIR] python-nosehtmloutput To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-nosehtmloutput/+bug/1420017/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1754015] Re: [SRU] nova-compute-kvm does not pull ipxe-qemu on non-amd64 archs
This bug was fixed in the package nova - 2:16.1.0-0ubuntu1~cloud0 --- nova (2:16.1.0-0ubuntu1~cloud0) xenial-pike; urgency=medium . * New upstream release for the Ubuntu Cloud Archive. . nova (2:16.1.0-0ubuntu1) artful; urgency=medium . [ James Page ] * Add Depends nova-compute-kvm -> ipxe-qemu to ensure that required ROM's are installed for all architectures (LP: #1754015). . [ Corey Bryant ] * New stable point release for OpenStack Pike (LP: #1758046). * d/p/aarch64-libvirt-compat.patch: Rebased and updated to mock os.path.exists return value to true in order to simulate _has_uefi_support returning true (LP: #1758060). ** Changed in: cloud-archive/pike Status: Fix Committed => Fix Released ** Changed in: cloud-archive/queens Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/1754015 Title: [SRU] nova-compute-kvm does not pull ipxe-qemu on non-amd64 archs To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1754015/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1763085] Re: Investigate updating to pacemaker 1.1.18 and corosync 2.4.3
Nish, Thanks very much for the update. I successfully performed some testing with a keystone cluster. The results are in the following paste: https://paste.ubuntu.com/p/Wtwnyvn8XZ/ Thanks, Corey -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1763085 Title: Investigate updating to pacemaker 1.1.18 and corosync 2.4.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1763085/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1744882] Re: Add SPEC_CTRL and IBRS changes
Regression testing for trusty-mitaka has successfully passed: == Totals == Ran: 102 tests in 1037.8303 sec. - Passed: 94 - Skipped: 8 - Expected Fail: 0 - Unexpected Success: 0 - Failed: 0 Sum of execute time for each test: 622.6697 sec. ** Tags removed: verification-mitaka-needed ** Tags added: verification-mitaka-done ** Changed in: cloud-archive/mitaka Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1744882 Title: Add SPEC_CTRL and IBRS changes To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1744882/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1744882] Re: Add SPEC_CTRL and IBRS changes
** Changed in: cloud-archive/ocata Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1744882 Title: Add SPEC_CTRL and IBRS changes To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1744882/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1752660] Re: python-cryptography missing cffi dependency
I've marked this incomplete until we can recreate it. ** Changed in: python-cryptography (Ubuntu Bionic) Status: Fix Released => Incomplete ** No longer affects: python-cryptography (Ubuntu Artful) ** No longer affects: python-cryptography (Ubuntu) ** No longer affects: python-cryptography (Ubuntu Xenial) ** No longer affects: python-cryptography (Ubuntu Bionic) ** Also affects: python-cryptography (Ubuntu) Importance: Undecided Status: New ** Changed in: python-cryptography (Ubuntu) Status: New => Incomplete ** No longer affects: cloud-archive ** No longer affects: cloud-archive/mitaka ** No longer affects: cloud-archive/newton ** No longer affects: cloud-archive/ocata ** No longer affects: cloud-archive/queens ** No longer affects: cloud-archive/pike -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to python-cryptography in Ubuntu. https://bugs.launchpad.net/bugs/1752660 Title: python-cryptography missing cffi dependency To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-cryptography/+bug/1752660/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1752660] Re: python-cryptography missing cffi dependency
Hi Graham, I don't think this is a dependency issue. I'm going to back out the changes I made earlier as I pulled the trigger too quickly with those. What would be good to know is what 'buf' is set to in your scenario. Here's a little script that hits the same path your traceback goes down. It runs successfully on xenial-queens for me. from cryptography.fernet import Fernet, MultiFernet key1 = Fernet(Fernet.generate_key()) key2 = Fernet(Fernet.generate_key()) f = MultiFernet([key1, key2]) token = f.encrypt(b"Secret message!") Thanks, Corey -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-cryptography in Ubuntu. https://bugs.launchpad.net/bugs/1752660 Title: python-cryptography missing cffi dependency To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1752660/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1752660] Re: python-cryptography missing cffi dependency
Graham, thanks that would be great. This will get you the new version: sudo add-apt-repository ppa:ubuntu-cloud-archive/queens-staging sudo apt update -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-cryptography in Ubuntu. https://bugs.launchpad.net/bugs/1752660 Title: python-cryptography missing cffi dependency To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1752660/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1752660] Re: python-cryptography missing cffi dependency
Graham, would you mind testing with a PPA? If you can let me know what release combination you're working with and I can get a PPA built. I've unsubscribed the SRU team for now as Tristan mentioned in the Debian bug that he didn't immediately see what the stack trace in the Ubuntu bug report has to do with cffi being installed or not. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-cryptography in Ubuntu. https://bugs.launchpad.net/bugs/1752660 Title: python-cryptography missing cffi dependency To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1752660/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1752660] Re: python-cryptography missing cffi dependency
I've uploaded a new fixed version of the python-cryptography to all affected releases. The Xenial (Mitaka) and Artful (Pike) versions will need to be reviewed by the SRU team before they are accepted into proposed and backported to the cloud-archive. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-cryptography in Ubuntu. https://bugs.launchpad.net/bugs/1752660 Title: python-cryptography missing cffi dependency To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1752660/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1752660] Re: python-cryptography missing cffi dependency
I think our long-term fix will come from the Debian maintainer's approach to adding dependencies. I'm going to fix this in Ubuntu for now by adding python-cffi to debian/control Depends. ** Summary changed: - keystone requires cffi to be installed for fernat tokens + python-cryptography missing cffi dependency ** Also affects: cloud-archive/mitaka Importance: Undecided Status: New ** Also affects: cloud-archive/queens Importance: High Status: Triaged ** Also affects: cloud-archive/newton Importance: Undecided Status: New ** Also affects: cloud-archive/pike Importance: Undecided Status: New ** Also affects: cloud-archive/ocata Importance: Undecided Status: New ** Changed in: cloud-archive/pike Status: New => Triaged ** Changed in: cloud-archive/ocata Status: New => Triaged ** Changed in: cloud-archive/newton Status: New => Triaged ** Changed in: cloud-archive/mitaka Status: New => Triaged ** Changed in: cloud-archive/pike Importance: Undecided => High ** Changed in: cloud-archive/ocata Importance: Undecided => High ** Changed in: cloud-archive/mitaka Importance: Undecided => High ** Changed in: cloud-archive/newton Importance: Undecided => High ** Also affects: keystone (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: python-cryptography (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: keystone (Ubuntu Bionic) Importance: Undecided Status: Invalid ** Also affects: python-cryptography (Ubuntu Bionic) Importance: High Status: Triaged ** Also affects: keystone (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: python-cryptography (Ubuntu Artful) Importance: Undecided Status: New ** Changed in: python-cryptography (Ubuntu Xenial) Status: New => Triaged ** No longer affects: keystone (Ubuntu Artful) ** No longer affects: keystone ** No longer affects: keystone (Ubuntu) ** No longer affects: keystone (Ubuntu Xenial) ** No longer affects: keystone (Ubuntu Bionic) ** Changed in: python-cryptography (Ubuntu Artful) Importance: Undecided => High ** Changed in: python-cryptography (Ubuntu Xenial) Importance: Undecided => High ** Changed in: python-cryptography (Ubuntu Artful) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-cryptography in Ubuntu. https://bugs.launchpad.net/bugs/1752660 Title: python-cryptography missing cffi dependency To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1752660/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1752660] Re: keystone requires cffi to be installed for fernat tokens
I've opened the following bug against the Debian package: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892112 ** Bug watch added: Debian Bug tracker #892112 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892112 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-cryptography in Ubuntu. https://bugs.launchpad.net/bugs/1752660 Title: keystone requires cffi to be installed for fernat tokens To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1752660/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
