Activity log for bug #1823872

Date Who What changed Old value New value Message
2019-04-09 10:15:17 Christian Ehrhardt  bug added bug
2019-04-09 10:16:34 Christian Ehrhardt  bug task added unattended-upgrades (Ubuntu)
2019-04-09 10:17:41 Christian Ehrhardt  description As reported on https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1820291/comments/20 We fixed an issue and we added workrounds since basic mv_conffile coudn't handle it and did all sort of upgrade tests. That all worked fine and moved the conffile. It was now reported that due to some pre-checks that unattended upgrades might do this might do some checks on its own. Next step: - check unattended upgrades through this change - check if it only affects cases were the former config was modified (minority) or the default file layout (majority) As reported on https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1820291/comments/20 We fixed an issue and we added workrounds since basic mv_conffile coudn't handle it and did all sort of upgrade tests. That all worked fine and moved the conffile. It was now reported that due to some pre-checks that unattended upgrades might do this might do some checks on its own. Next step: - check unattended upgrades through this change - check if it only affects cases were the former config was modified (minority) or the default file layout (majority) --- original report copied --- just wanted to add: This bug also crashes unattended-upgrade and thus prevents security updates on 18.04: root@mailin1:~# unattended-upgrade Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 1998, in <module> sys.exit(main(options)) File "/usr/bin/unattended-upgrade", line 1714, in main if conffile_prompt(item.destfile): File "/usr/bin/unattended-upgrade", line 929, in conffile_prompt with open(prefix + conf_file, 'rb') as fp: IsADirectoryError: [Errno 21] Is a directory: '/etc/qemu/fsfreeze-hook' Basically, unattended-upgrade wants to compare old/new conffiles and doesn't like it when the old conffile turns out to be a directory... This prevents security updates to be installed. The unattended-upgrade logs do not contain the trace, only the messages: 2019-04-05 13:24:24,851 INFO Initial blacklisted packages: 2019-04-05 13:24:24,853 INFO Initial whitelisted packages: 2019-04-05 13:24:24,853 INFO Starting unattended upgrades script 2019-04-05 13:24:24,854 INFO Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic' And that's it. You can't really get out of this without manually running 'apt-get install qemu-guest-agent' because at this point, unattended-upgrade can't update itself anymore.
2019-04-09 11:41:53 Launchpad Janitor qemu (Ubuntu): status New Confirmed
2019-04-09 11:41:53 Launchpad Janitor unattended-upgrades (Ubuntu): status New Confirmed
2019-04-09 14:04:59 Christian Ehrhardt  description As reported on https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1820291/comments/20 We fixed an issue and we added workrounds since basic mv_conffile coudn't handle it and did all sort of upgrade tests. That all worked fine and moved the conffile. It was now reported that due to some pre-checks that unattended upgrades might do this might do some checks on its own. Next step: - check unattended upgrades through this change - check if it only affects cases were the former config was modified (minority) or the default file layout (majority) --- original report copied --- just wanted to add: This bug also crashes unattended-upgrade and thus prevents security updates on 18.04: root@mailin1:~# unattended-upgrade Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 1998, in <module> sys.exit(main(options)) File "/usr/bin/unattended-upgrade", line 1714, in main if conffile_prompt(item.destfile): File "/usr/bin/unattended-upgrade", line 929, in conffile_prompt with open(prefix + conf_file, 'rb') as fp: IsADirectoryError: [Errno 21] Is a directory: '/etc/qemu/fsfreeze-hook' Basically, unattended-upgrade wants to compare old/new conffiles and doesn't like it when the old conffile turns out to be a directory... This prevents security updates to be installed. The unattended-upgrade logs do not contain the trace, only the messages: 2019-04-05 13:24:24,851 INFO Initial blacklisted packages: 2019-04-05 13:24:24,853 INFO Initial whitelisted packages: 2019-04-05 13:24:24,853 INFO Starting unattended upgrades script 2019-04-05 13:24:24,854 INFO Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic' And that's it. You can't really get out of this without manually running 'apt-get install qemu-guest-agent' because at this point, unattended-upgrade can't update itself anymore. [Impact] * If an update has a new conffile at a path that in a former version was a directory like old: /a/b/c new: a/b Here b is the new file name and was a directory in the old version. Then unattended upgrades breaks on installing such a package. * a recent qemu update has such a case and due to that triggered the issue in >=Bionic * The fix is to harden unattended upgrades to be able to handle the case without aborting. [Test Case] Get a qemu guest e.g. of Bionic before the update to 1:2.11+dfsg-1ubuntu7.12 That can be done with: $ time uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=bionic $ uvt-kvm create --password ubuntu bionic-testuu arch=amd64 release=bionic label=daily Log in and apt update & upgrade all packages, then Install the release level qemu in there. $ uvt-kvm ssh bionic-testuu $ sudo apt update $ sudo apt dist-upgrade $ sudo apt install unattended-upgrades $ sudo apt install qemu-guest-agent=1:2.11+dfsg-1ubuntu7 All before was preparation, now force the unattended upgrade to trigger the bug. $ sudo unattended-upgrade -d With the bug you'll find some error like: found pkg: qemu-guest-agent conffile line: /etc/init.d/qemu-guest-agent f61a64ac1e48993023018fd1cff85191 current md5: f61a64ac1e48993023018fd1cff85191 conffile line: /etc/qemu/fsfreeze-hook/fsfreeze-hook 15f6ff42cbc5550a07ee21c2a471d905 /etc/qemu/fsfreeze-hook/fsfreeze-hook not in package conffiles /etc/init.d/qemu-guest-agent /etc/qemu/fsfreeze-hook found conffile /etc/qemu/fsfreeze-hook in new pkg but on dpkg status Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 2057, in <module> sys.exit(main(options)) File "/usr/bin/unattended-upgrade", line 1773, in main if conffile_prompt(item.destfile): File "/usr/bin/unattended-upgrade", line 988, in conffile_prompt with open(prefix + conf_file, 'rb') as fp: IsADirectoryError: [Errno 21] Is a directory: '/etc/qemu/fsfreeze-hook' [Regression Potential] TODO: rbalint who writes the fix * discussion of how regressions are most likely to manifest as a result of this change. * It is assumed that any SRU candidate patch is well-tested before upload and has a low overall risk of regression, but it's important to make the effort to think about what ''could'' happen in the event of a regression. * This both shows the SRU team that the risks have been considered, and provides guidance to testers in regression-testing the SRU. [Other Info] * n/a --- As reported on https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1820291/comments/20 We fixed an issue and we added workrounds since basic mv_conffile coudn't handle it and did all sort of upgrade tests. That all worked fine and moved the conffile. It was now reported that due to some pre-checks that unattended upgrades might do this might do some checks on its own. Next step: - check unattended upgrades through this change - check if it only affects cases were the former config was modified (minority) or the default file layout (majority) --- original report copied --- just wanted to add: This bug also crashes unattended-upgrade and thus prevents security updates on 18.04: root@mailin1:~# unattended-upgrade Traceback (most recent call last):   File "/usr/bin/unattended-upgrade", line 1998, in <module>     sys.exit(main(options))   File "/usr/bin/unattended-upgrade", line 1714, in main     if conffile_prompt(item.destfile):   File "/usr/bin/unattended-upgrade", line 929, in conffile_prompt     with open(prefix + conf_file, 'rb') as fp: IsADirectoryError: [Errno 21] Is a directory: '/etc/qemu/fsfreeze-hook' Basically, unattended-upgrade wants to compare old/new conffiles and doesn't like it when the old conffile turns out to be a directory... This prevents security updates to be installed. The unattended-upgrade logs do not contain the trace, only the messages: 2019-04-05 13:24:24,851 INFO Initial blacklisted packages: 2019-04-05 13:24:24,853 INFO Initial whitelisted packages: 2019-04-05 13:24:24,853 INFO Starting unattended upgrades script 2019-04-05 13:24:24,854 INFO Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic' And that's it. You can't really get out of this without manually running 'apt-get install qemu-guest-agent' because at this point, unattended-upgrade can't update itself anymore.
2019-04-10 05:57:14 Christian Ehrhardt  unattended-upgrades (Ubuntu): assignee Balint Reczey (rbalint)
2019-04-10 05:57:21 Christian Ehrhardt  qemu (Ubuntu): status Confirmed Invalid
2019-04-10 12:38:05 Francis Ginther tags id-5caddb1e34438017500c9b85
2019-04-11 21:23:15 Balint Reczey unattended-upgrades (Ubuntu): status Confirmed Fix Committed
2019-04-12 12:24:49 Launchpad Janitor unattended-upgrades (Ubuntu): status Fix Committed Fix Released
2019-04-15 06:47:19 Christian Ehrhardt  nominated for series Ubuntu Cosmic
2019-04-15 06:47:19 Christian Ehrhardt  bug task added qemu (Ubuntu Cosmic)
2019-04-15 06:47:19 Christian Ehrhardt  bug task added unattended-upgrades (Ubuntu Cosmic)
2019-04-15 06:47:19 Christian Ehrhardt  nominated for series Ubuntu Bionic
2019-04-15 06:47:19 Christian Ehrhardt  bug task added qemu (Ubuntu Bionic)
2019-04-15 06:47:19 Christian Ehrhardt  bug task added unattended-upgrades (Ubuntu Bionic)
2019-04-15 06:47:26 Christian Ehrhardt  bug task deleted qemu (Ubuntu Bionic)
2019-04-15 06:47:31 Christian Ehrhardt  bug task deleted qemu (Ubuntu Cosmic)
2019-04-15 06:47:40 Christian Ehrhardt  unattended-upgrades (Ubuntu Bionic): assignee Balint Reczey (rbalint)
2019-04-15 06:47:46 Christian Ehrhardt  unattended-upgrades (Ubuntu Cosmic): assignee Balint Reczey (rbalint)
2019-04-15 06:47:53 Christian Ehrhardt  unattended-upgrades (Ubuntu Bionic): importance Undecided High
2019-04-15 06:47:54 Christian Ehrhardt  unattended-upgrades (Ubuntu Cosmic): importance Undecided High
2019-04-15 06:49:24 Christian Ehrhardt  nominated for series Ubuntu Xenial
2019-04-15 06:49:24 Christian Ehrhardt  bug task added qemu (Ubuntu Xenial)
2019-04-15 06:49:24 Christian Ehrhardt  bug task added unattended-upgrades (Ubuntu Xenial)
2019-04-15 06:49:24 Christian Ehrhardt  nominated for series Ubuntu Trusty
2019-04-15 06:49:24 Christian Ehrhardt  bug task added qemu (Ubuntu Trusty)
2019-04-15 06:49:24 Christian Ehrhardt  bug task added unattended-upgrades (Ubuntu Trusty)
2019-04-15 06:49:32 Christian Ehrhardt  bug task deleted qemu (Ubuntu Xenial)
2019-04-15 06:49:36 Christian Ehrhardt  bug task deleted qemu (Ubuntu Trusty)
2019-04-15 06:49:43 Christian Ehrhardt  unattended-upgrades (Ubuntu Xenial): importance Undecided Medium
2019-04-15 06:49:45 Christian Ehrhardt  unattended-upgrades (Ubuntu Trusty): importance Undecided Medium
2019-04-15 06:49:46 Christian Ehrhardt  unattended-upgrades (Ubuntu Trusty): assignee Balint Reczey (rbalint)
2019-04-15 06:49:50 Christian Ehrhardt  unattended-upgrades (Ubuntu Xenial): assignee Balint Reczey (rbalint)
2019-04-29 14:39:24 Balint Reczey description [Impact] * If an update has a new conffile at a path that in a former version was a directory like old: /a/b/c new: a/b Here b is the new file name and was a directory in the old version. Then unattended upgrades breaks on installing such a package. * a recent qemu update has such a case and due to that triggered the issue in >=Bionic * The fix is to harden unattended upgrades to be able to handle the case without aborting. [Test Case] Get a qemu guest e.g. of Bionic before the update to 1:2.11+dfsg-1ubuntu7.12 That can be done with: $ time uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=bionic $ uvt-kvm create --password ubuntu bionic-testuu arch=amd64 release=bionic label=daily Log in and apt update & upgrade all packages, then Install the release level qemu in there. $ uvt-kvm ssh bionic-testuu $ sudo apt update $ sudo apt dist-upgrade $ sudo apt install unattended-upgrades $ sudo apt install qemu-guest-agent=1:2.11+dfsg-1ubuntu7 All before was preparation, now force the unattended upgrade to trigger the bug. $ sudo unattended-upgrade -d With the bug you'll find some error like: found pkg: qemu-guest-agent conffile line: /etc/init.d/qemu-guest-agent f61a64ac1e48993023018fd1cff85191 current md5: f61a64ac1e48993023018fd1cff85191 conffile line: /etc/qemu/fsfreeze-hook/fsfreeze-hook 15f6ff42cbc5550a07ee21c2a471d905 /etc/qemu/fsfreeze-hook/fsfreeze-hook not in package conffiles /etc/init.d/qemu-guest-agent /etc/qemu/fsfreeze-hook found conffile /etc/qemu/fsfreeze-hook in new pkg but on dpkg status Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 2057, in <module> sys.exit(main(options)) File "/usr/bin/unattended-upgrade", line 1773, in main if conffile_prompt(item.destfile): File "/usr/bin/unattended-upgrade", line 988, in conffile_prompt with open(prefix + conf_file, 'rb') as fp: IsADirectoryError: [Errno 21] Is a directory: '/etc/qemu/fsfreeze-hook' [Regression Potential] TODO: rbalint who writes the fix * discussion of how regressions are most likely to manifest as a result of this change. * It is assumed that any SRU candidate patch is well-tested before upload and has a low overall risk of regression, but it's important to make the effort to think about what ''could'' happen in the event of a regression. * This both shows the SRU team that the risks have been considered, and provides guidance to testers in regression-testing the SRU. [Other Info] * n/a --- As reported on https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1820291/comments/20 We fixed an issue and we added workrounds since basic mv_conffile coudn't handle it and did all sort of upgrade tests. That all worked fine and moved the conffile. It was now reported that due to some pre-checks that unattended upgrades might do this might do some checks on its own. Next step: - check unattended upgrades through this change - check if it only affects cases were the former config was modified (minority) or the default file layout (majority) --- original report copied --- just wanted to add: This bug also crashes unattended-upgrade and thus prevents security updates on 18.04: root@mailin1:~# unattended-upgrade Traceback (most recent call last):   File "/usr/bin/unattended-upgrade", line 1998, in <module>     sys.exit(main(options))   File "/usr/bin/unattended-upgrade", line 1714, in main     if conffile_prompt(item.destfile):   File "/usr/bin/unattended-upgrade", line 929, in conffile_prompt     with open(prefix + conf_file, 'rb') as fp: IsADirectoryError: [Errno 21] Is a directory: '/etc/qemu/fsfreeze-hook' Basically, unattended-upgrade wants to compare old/new conffiles and doesn't like it when the old conffile turns out to be a directory... This prevents security updates to be installed. The unattended-upgrade logs do not contain the trace, only the messages: 2019-04-05 13:24:24,851 INFO Initial blacklisted packages: 2019-04-05 13:24:24,853 INFO Initial whitelisted packages: 2019-04-05 13:24:24,853 INFO Starting unattended upgrades script 2019-04-05 13:24:24,854 INFO Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic' And that's it. You can't really get out of this without manually running 'apt-get install qemu-guest-agent' because at this point, unattended-upgrade can't update itself anymore. [Impact]  * If an update has a new conffile at a path that in a former version was    a directory like     old: /a/b/c     new: a/b    Here b is the new file name and was a directory in the old version.    Then unattended upgrades breaks on installing such a package.  * a recent qemu update has such a case and due to that triggered the    issue in >=Bionic  * The fix is to harden unattended upgrades to be able to handle the case    without aborting. [Test Case] Get a qemu guest e.g. of Bionic before the update to 1:2.11+dfsg-1ubuntu7.12 That can be done with:   $ time uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=bionic   $ uvt-kvm create --password ubuntu bionic-testuu arch=amd64 release=bionic label=daily Log in and apt update & upgrade all packages, then Install the release level qemu in there.   $ uvt-kvm ssh bionic-testuu   $ sudo apt update   $ sudo apt dist-upgrade   $ sudo apt install unattended-upgrades   $ sudo apt install qemu-guest-agent=1:2.11+dfsg-1ubuntu7 All before was preparation, now force the unattended upgrade to trigger the bug.   $ sudo unattended-upgrade -d With the bug you'll find some error like: found pkg: qemu-guest-agent conffile line: /etc/init.d/qemu-guest-agent f61a64ac1e48993023018fd1cff85191 current md5: f61a64ac1e48993023018fd1cff85191 conffile line: /etc/qemu/fsfreeze-hook/fsfreeze-hook 15f6ff42cbc5550a07ee21c2a471d905 /etc/qemu/fsfreeze-hook/fsfreeze-hook not in package conffiles /etc/init.d/qemu-guest-agent /etc/qemu/fsfreeze-hook found conffile /etc/qemu/fsfreeze-hook in new pkg but on dpkg status Traceback (most recent call last):   File "/usr/bin/unattended-upgrade", line 2057, in <module>     sys.exit(main(options))   File "/usr/bin/unattended-upgrade", line 1773, in main     if conffile_prompt(item.destfile):   File "/usr/bin/unattended-upgrade", line 988, in conffile_prompt     with open(prefix + conf_file, 'rb') as fp: IsADirectoryError: [Errno 21] Is a directory: '/etc/qemu/fsfreeze-hook' [Regression Potential] * The fix is trying to detect moved conffiles by looking for /etc/foo/foo when the new package ships /etc/foo and /etc/foo is not a known conffile and also checking the renames in the opposite direction. The potential regression is breaking the logic for detecting changed conffiles and either holding back a package for no reason or trying to install a package with a modified conffile on the system and aborting the upgrade in the middle due to the appearing conffile prompt. To avoid such regressions the test_conffile.py tests are extended to cover rename scenarios. [Other Info]  * n/a --- As reported on https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1820291/comments/20 We fixed an issue and we added workrounds since basic mv_conffile coudn't handle it and did all sort of upgrade tests. That all worked fine and moved the conffile. It was now reported that due to some pre-checks that unattended upgrades might do this might do some checks on its own. Next step: - check unattended upgrades through this change - check if it only affects cases were the former config was modified (minority) or the default file layout (majority) --- original report copied --- just wanted to add: This bug also crashes unattended-upgrade and thus prevents security updates on 18.04: root@mailin1:~# unattended-upgrade Traceback (most recent call last):   File "/usr/bin/unattended-upgrade", line 1998, in <module>     sys.exit(main(options))   File "/usr/bin/unattended-upgrade", line 1714, in main     if conffile_prompt(item.destfile):   File "/usr/bin/unattended-upgrade", line 929, in conffile_prompt     with open(prefix + conf_file, 'rb') as fp: IsADirectoryError: [Errno 21] Is a directory: '/etc/qemu/fsfreeze-hook' Basically, unattended-upgrade wants to compare old/new conffiles and doesn't like it when the old conffile turns out to be a directory... This prevents security updates to be installed. The unattended-upgrade logs do not contain the trace, only the messages: 2019-04-05 13:24:24,851 INFO Initial blacklisted packages: 2019-04-05 13:24:24,853 INFO Initial whitelisted packages: 2019-04-05 13:24:24,853 INFO Starting unattended upgrades script 2019-04-05 13:24:24,854 INFO Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic' And that's it. You can't really get out of this without manually running 'apt-get install qemu-guest-agent' because at this point, unattended-upgrade can't update itself anymore.
2019-04-29 14:54:15 Łukasz Zemczak unattended-upgrades (Ubuntu Disco): status New Fix Committed
2019-04-29 14:54:17 Łukasz Zemczak bug added subscriber Ubuntu Stable Release Updates Team
2019-04-29 14:54:18 Łukasz Zemczak bug added subscriber SRU Verification
2019-04-29 14:54:22 Łukasz Zemczak tags id-5caddb1e34438017500c9b85 id-5caddb1e34438017500c9b85 verification-needed verification-needed-disco
2019-04-30 08:42:36 Łukasz Zemczak unattended-upgrades (Ubuntu Cosmic): status New Fix Committed
2019-04-30 08:42:42 Łukasz Zemczak tags id-5caddb1e34438017500c9b85 verification-needed verification-needed-disco id-5caddb1e34438017500c9b85 verification-needed verification-needed-cosmic verification-needed-disco
2019-04-30 09:10:57 Łukasz Zemczak unattended-upgrades (Ubuntu Bionic): status New Fix Committed
2019-04-30 09:11:01 Łukasz Zemczak tags id-5caddb1e34438017500c9b85 verification-needed verification-needed-cosmic verification-needed-disco id-5caddb1e34438017500c9b85 verification-needed verification-needed-bionic verification-needed-cosmic verification-needed-disco
2019-04-30 10:01:17 Łukasz Zemczak unattended-upgrades (Ubuntu Xenial): status New Fix Committed
2019-04-30 10:01:23 Łukasz Zemczak tags id-5caddb1e34438017500c9b85 verification-needed verification-needed-bionic verification-needed-cosmic verification-needed-disco id-5caddb1e34438017500c9b85 verification-needed verification-needed-bionic verification-needed-cosmic verification-needed-disco verification-needed-xenial
2019-04-30 11:17:02 Christian Ehrhardt  tags id-5caddb1e34438017500c9b85 verification-needed verification-needed-bionic verification-needed-cosmic verification-needed-disco verification-needed-xenial id-5caddb1e34438017500c9b85 verification-done-bionic verification-needed verification-needed-cosmic verification-needed-disco verification-needed-xenial
2019-05-02 10:10:44 Launchpad Janitor unattended-upgrades (Ubuntu Trusty): status New Confirmed
2019-05-03 05:51:13 Christian Ehrhardt  tags id-5caddb1e34438017500c9b85 verification-done-bionic verification-needed verification-needed-cosmic verification-needed-disco verification-needed-xenial id-5caddb1e34438017500c9b85 verification-done-bionic verification-done-cosmic verification-needed verification-needed-disco verification-needed-xenial
2019-05-03 14:23:24 Balint Reczey tags id-5caddb1e34438017500c9b85 verification-done-bionic verification-done-cosmic verification-needed verification-needed-disco verification-needed-xenial id-5caddb1e34438017500c9b85 verification-done-bionic verification-done-cosmic verification-done-disco verification-needed verification-needed-xenial
2019-05-03 14:46:55 Balint Reczey tags id-5caddb1e34438017500c9b85 verification-done-bionic verification-done-cosmic verification-done-disco verification-needed verification-needed-xenial id-5caddb1e34438017500c9b85 verification-done verification-done-bionic verification-done-cosmic verification-done-disco verification-done-xenial
2019-05-03 19:45:36 Mathew Hodson unattended-upgrades (Ubuntu Disco): importance Undecided High
2019-05-03 19:45:40 Mathew Hodson unattended-upgrades (Ubuntu): importance Undecided High
2019-05-03 19:49:31 Mathew Hodson bug task deleted qemu (Ubuntu)
2019-05-07 09:50:13 Łukasz Zemczak removed subscriber Ubuntu Stable Release Updates Team
2019-05-07 09:52:17 Launchpad Janitor unattended-upgrades (Ubuntu Cosmic): status Fix Committed Fix Released
2019-05-07 09:53:44 Launchpad Janitor unattended-upgrades (Ubuntu Bionic): status Fix Committed Fix Released
2019-05-07 09:58:10 Launchpad Janitor unattended-upgrades (Ubuntu Xenial): status Fix Committed Fix Released
2019-05-07 10:00:18 Launchpad Janitor unattended-upgrades (Ubuntu Disco): status Fix Committed Fix Released
2019-05-23 17:06:26 Balint Reczey bug task added qemu (Ubuntu)
2019-05-23 17:12:39 Balint Reczey attachment added qemu_2.11+dfsg-1ubuntu7.14.patch https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1823872/+attachment/5266072/+files/qemu_2.11+dfsg-1ubuntu7.14.patch
2019-05-23 17:51:42 Balint Reczey information type Public Public Security
2019-05-23 20:21:13 Ubuntu Foundations Team Bug Bot tags id-5caddb1e34438017500c9b85 verification-done verification-done-bionic verification-done-cosmic verification-done-disco verification-done-xenial id-5caddb1e34438017500c9b85 patch verification-done verification-done-bionic verification-done-cosmic verification-done-disco verification-done-xenial
2019-05-24 14:34:36 Launchpad Janitor qemu (Ubuntu): status New Fix Released
2019-05-24 14:34:37 Launchpad Janitor qemu (Ubuntu): status New Fix Released
2021-06-12 19:29:24 Balint Reczey unattended-upgrades (Ubuntu Trusty): assignee Balint Reczey (rbalint)