Activity log for bug #1821376

Date Who What changed Old value New value Message
2019-03-22 16:35:35 Balint Reczey bug added bug
2019-03-22 16:35:55 Balint Reczey description Packages kept back are listed in the email report, but it is not clear from which origins they are installable. This information may help administrators to decide if the package needs to be manually upgraded. Packages kept back are listed in the email report, but it is not clear from which origins they are installable. This information may help administrators to decide if the packages need to be manually upgraded.
2019-04-26 13:37:45 Launchpad Janitor unattended-upgrades (Ubuntu): status New Fix Released
2019-10-18 09:48:06 Balint Reczey description Packages kept back are listed in the email report, but it is not clear from which origins they are installable. This information may help administrators to decide if the packages need to be manually upgraded. [Impact] * Packages kept back are listed in the email report, but it is not clear from which origins they are installable. This information may help administrators to decide if the packages need to be manually upgraded. [Test Case] * test_mail.py test is updated to check if the kept back packages are reported per origin and this is checked at build time. * For manual testing: 1. Configure u-u to allow upgrades from the -updates pocket and send email with the upgrade report. 2. Set up the system to have a few packages upgradable from both the -security and -updates pockets. 3. Mark a subset of packages which are upgradable as held, marking packages from each of the pockets. 4. Run u-u and observe the kept packages listed in the email. Each package is listed only in the allowed origin providing the highest version. (LP: #1848697 covers listing them in all origins from which the packages could be upgraded to.) [Regression Potential] * Unattended upgrades may crash while trying to perform updates or while trying to send the summary email. Build-time tests and autopkgtests include testing both functions.
2019-10-24 20:23:53 Brian Murray unattended-upgrades (Ubuntu Disco): status New Fix Committed
2019-10-24 20:23:54 Brian Murray bug added subscriber Ubuntu Stable Release Updates Team
2019-10-24 20:23:56 Brian Murray bug added subscriber SRU Verification
2019-10-24 20:23:59 Brian Murray tags verification-needed verification-needed-disco
2019-10-24 20:29:05 Brian Murray unattended-upgrades (Ubuntu Bionic): status New Fix Committed
2019-10-24 20:29:11 Brian Murray tags verification-needed verification-needed-disco verification-needed verification-needed-bionic verification-needed-disco
2019-10-24 20:31:28 Brian Murray unattended-upgrades (Ubuntu Xenial): status New Fix Committed
2019-10-24 20:31:33 Brian Murray tags verification-needed verification-needed-bionic verification-needed-disco verification-needed verification-needed-bionic verification-needed-disco verification-needed-xenial
2019-11-01 17:57:45 Balint Reczey description [Impact] * Packages kept back are listed in the email report, but it is not clear from which origins they are installable. This information may help administrators to decide if the packages need to be manually upgraded. [Test Case] * test_mail.py test is updated to check if the kept back packages are reported per origin and this is checked at build time. * For manual testing: 1. Configure u-u to allow upgrades from the -updates pocket and send email with the upgrade report. 2. Set up the system to have a few packages upgradable from both the -security and -updates pockets. 3. Mark a subset of packages which are upgradable as held, marking packages from each of the pockets. 4. Run u-u and observe the kept packages listed in the email. Each package is listed only in the allowed origin providing the highest version. (LP: #1848697 covers listing them in all origins from which the packages could be upgraded to.) [Regression Potential] * Unattended upgrades may crash while trying to perform updates or while trying to send the summary email. Build-time tests and autopkgtests include testing both functions. [Impact] * Packages kept back are listed in the email report, but it is not clear from which origins they are installable. This information may help administrators to decide if the packages need to be manually upgraded. [Test Case] * test_mail.py test is updated to check if the kept back packages are reported per origin and this is checked at build time. * For manual testing:   1. Configure u-u to allow upgrades from the -updates pocket and send email with the upgrade report.   2. Set up the system to have a few packages upgradable from both the -security and -updates pockets.   3. Mark a subset of packages which are upgradable as held, marking packages from each of the pockets.   4. Run u-u and observe the kept packages listed in the email. Each package is listed only in the allowed origin providing the highest version. (LP: #1848697 covers listing them in all origins from which the packages could be upgraded to.) [Regression Potential] * Unattended upgrades may crash while trying to perform updates or while trying to send the summary email. Build-time tests and autopkgtests include testing both functions.
2019-11-01 18:00:56 Balint Reczey tags verification-needed verification-needed-bionic verification-needed-disco verification-needed-xenial verification-done verification-done-bionic verification-done-disco verification-done-xenial
2019-11-07 00:07:00 Launchpad Janitor unattended-upgrades (Ubuntu Disco): status Fix Committed Fix Released
2019-11-07 00:07:12 Brian Murray removed subscriber Ubuntu Stable Release Updates Team
2019-11-07 00:08:10 Launchpad Janitor unattended-upgrades (Ubuntu Bionic): status Fix Committed Fix Released
2019-11-07 00:09:12 Launchpad Janitor unattended-upgrades (Ubuntu Xenial): status Fix Committed Fix Released