| 2019-04-03 19:39:05 |
Steve Langasek |
bug |
|
|
added bug |
| 2019-04-04 12:24:51 |
Francis Ginther |
tags |
|
id-5ca50c3568756c4a351b6f5f |
|
| 2019-04-04 15:37:24 |
Balint Reczey |
unattended-upgrades (Ubuntu): status |
New |
Confirmed |
|
| 2019-05-23 11:21:11 |
Balint Reczey |
unattended-upgrades (Ubuntu): status |
Confirmed |
In Progress |
|
| 2019-07-12 02:04:36 |
Launchpad Janitor |
unattended-upgrades (Ubuntu): status |
In Progress |
Fix Released |
|
| 2019-09-19 11:46:50 |
Balint Reczey |
nominated for series |
|
Ubuntu Disco |
|
| 2019-09-19 11:46:50 |
Balint Reczey |
bug task added |
|
unattended-upgrades (Ubuntu Disco) |
|
| 2019-09-19 11:46:50 |
Balint Reczey |
nominated for series |
|
Ubuntu Bionic |
|
| 2019-09-19 11:46:50 |
Balint Reczey |
bug task added |
|
unattended-upgrades (Ubuntu Bionic) |
|
| 2019-09-19 11:46:59 |
Balint Reczey |
unattended-upgrades (Ubuntu Bionic): status |
New |
Confirmed |
|
| 2019-09-19 11:47:02 |
Balint Reczey |
unattended-upgrades (Ubuntu Disco): status |
New |
Confirmed |
|
| 2019-10-18 11:15:26 |
Balint Reczey |
description |
Currently we have the following pieces as part of the default UX on Ubuntu 18.04 and later:
1) unattended-upgrades automatically installs security updates daily by default
2) the motd reports the number of available updates, including security updates.
A user who knows about 1) also knows that a non-zero number of pending security updates listed in 2) is nothing to worry about.
However, unattended-upgrades will also cleverly detect when a security update cannot safely be installed non-interactively due to conffile changes on the system.
In this case, unattended-upgrades should also inform the user via the motd that these updates are not being installed. Otherwise, there's nothing to tell the user that the non-zero count of available security updates in motd is a *problem*.
Suggested wording:
N security updates will not be automatically installed due to local changes.
See /var/log/foo for details. |
[Impact]
* MOTD does not go into details about upgradable packages being security fixes or just normal updates.
* Users should be made aware if some of the security updates could not have been applied.
* The fix is adding a snipped to MOTD where the number of packages kept back by unattended-upgrades is shown.
[Test Case]
* The debian/tests/upgrade-all-security is extended to check if the number of kept back packages are shown in MOTD and a new test is added (test/test_motd.py) to check if the list of kept back packages are saved properly.
* To test the fix manually:
1. Mark a package upgradable from the -security pocket as held, then run unattended-upgrades.
2. Observe MOTD messate showing the number of packages being kept back.
[Regression Potential]
* Unattended-upgrades may crash when saving kept packages and always return with failure. MOTD may hang or print error while printing the packages kept back by u-u.
[Original Bug Text]
Currently we have the following pieces as part of the default UX on Ubuntu 18.04 and later:
1) unattended-upgrades automatically installs security updates daily by default
2) the motd reports the number of available updates, including security updates.
A user who knows about 1) also knows that a non-zero number of pending security updates listed in 2) is nothing to worry about.
However, unattended-upgrades will also cleverly detect when a security update cannot safely be installed non-interactively due to conffile changes on the system.
In this case, unattended-upgrades should also inform the user via the motd that these updates are not being installed. Otherwise, there's nothing to tell the user that the non-zero count of available security updates in motd is a *problem*.
Suggested wording:
N security updates will not be automatically installed due to local changes.
See /var/log/foo for details. |
|
| 2019-10-24 20:24:04 |
Brian Murray |
unattended-upgrades (Ubuntu Disco): status |
Confirmed |
Fix Committed |
|
| 2019-10-24 20:24:06 |
Brian Murray |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2019-10-24 20:24:08 |
Brian Murray |
bug |
|
|
added subscriber SRU Verification |
| 2019-10-24 20:24:11 |
Brian Murray |
tags |
id-5ca50c3568756c4a351b6f5f |
id-5ca50c3568756c4a351b6f5f verification-needed verification-needed-disco |
|
| 2019-10-24 20:29:15 |
Brian Murray |
unattended-upgrades (Ubuntu Bionic): status |
Confirmed |
Fix Committed |
|
| 2019-10-24 20:29:20 |
Brian Murray |
tags |
id-5ca50c3568756c4a351b6f5f verification-needed verification-needed-disco |
id-5ca50c3568756c4a351b6f5f verification-needed verification-needed-bionic verification-needed-disco |
|
| 2019-10-24 20:31:41 |
Brian Murray |
unattended-upgrades (Ubuntu Xenial): status |
New |
Fix Committed |
|
| 2019-10-24 20:31:47 |
Brian Murray |
tags |
id-5ca50c3568756c4a351b6f5f verification-needed verification-needed-bionic verification-needed-disco |
id-5ca50c3568756c4a351b6f5f verification-needed verification-needed-bionic verification-needed-disco verification-needed-xenial |
|
| 2019-11-01 17:22:16 |
Balint Reczey |
tags |
id-5ca50c3568756c4a351b6f5f verification-needed verification-needed-bionic verification-needed-disco verification-needed-xenial |
id-5ca50c3568756c4a351b6f5f verification-done-disco verification-needed verification-needed-bionic verification-needed-xenial |
|
| 2019-11-01 17:28:44 |
Balint Reczey |
description |
[Impact]
* MOTD does not go into details about upgradable packages being security fixes or just normal updates.
* Users should be made aware if some of the security updates could not have been applied.
* The fix is adding a snipped to MOTD where the number of packages kept back by unattended-upgrades is shown.
[Test Case]
* The debian/tests/upgrade-all-security is extended to check if the number of kept back packages are shown in MOTD and a new test is added (test/test_motd.py) to check if the list of kept back packages are saved properly.
* To test the fix manually:
1. Mark a package upgradable from the -security pocket as held, then run unattended-upgrades.
2. Observe MOTD messate showing the number of packages being kept back.
[Regression Potential]
* Unattended-upgrades may crash when saving kept packages and always return with failure. MOTD may hang or print error while printing the packages kept back by u-u.
[Original Bug Text]
Currently we have the following pieces as part of the default UX on Ubuntu 18.04 and later:
1) unattended-upgrades automatically installs security updates daily by default
2) the motd reports the number of available updates, including security updates.
A user who knows about 1) also knows that a non-zero number of pending security updates listed in 2) is nothing to worry about.
However, unattended-upgrades will also cleverly detect when a security update cannot safely be installed non-interactively due to conffile changes on the system.
In this case, unattended-upgrades should also inform the user via the motd that these updates are not being installed. Otherwise, there's nothing to tell the user that the non-zero count of available security updates in motd is a *problem*.
Suggested wording:
N security updates will not be automatically installed due to local changes.
See /var/log/foo for details. |
[Impact]
* MOTD does not go into details about upgradable packages being security fixes or just normal updates.
* Users should be made aware if some of the security updates could not have been applied.
* The fix is adding a snipped to MOTD where the number of packages kept back by unattended-upgrades is shown.
[Test Case]
* The debian/tests/upgrade-all-security is extended to check if the number of kept back packages are shown in MOTD and a new test is added (test/test_motd.py) to check if the list of kept back packages are saved properly.
* To test the fix manually:
1. Mark a package upgradable from the -security pocket as held, then run unattended-upgrades.
2. Observe MOTD messate showing the number of packages being kept back.
[Regression Potential]
* Unattended-upgrades may crash when saving kept packages and always return with failure. MOTD may hang or print error while printing the packages kept back by u-u.
* It is not a regression, but the log referenced in MOTD does not always contain explanation why each package was kept back, unless debugging is enabled. One case where packages are not mentioned in the log is when the packages are held using 'apt-mark hold' command.
[Original Bug Text]
Currently we have the following pieces as part of the default UX on Ubuntu 18.04 and later:
1) unattended-upgrades automatically installs security updates daily by default
2) the motd reports the number of available updates, including security updates.
A user who knows about 1) also knows that a non-zero number of pending security updates listed in 2) is nothing to worry about.
However, unattended-upgrades will also cleverly detect when a security update cannot safely be installed non-interactively due to conffile changes on the system.
In this case, unattended-upgrades should also inform the user via the motd that these updates are not being installed. Otherwise, there's nothing to tell the user that the non-zero count of available security updates in motd is a *problem*.
Suggested wording:
N security updates will not be automatically installed due to local changes.
See /var/log/foo for details. |
|
| 2019-11-01 17:30:50 |
Balint Reczey |
tags |
id-5ca50c3568756c4a351b6f5f verification-done-disco verification-needed verification-needed-bionic verification-needed-xenial |
id-5ca50c3568756c4a351b6f5f 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:16 |
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 |
|
