unattended-upgrades should tell the user (via motd) when security updates are held back
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
unattended-upgrades (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned | ||
Bionic |
Fix Released
|
Undecided
|
Unassigned | ||
Disco |
Fix Released
|
Undecided
|
Unassigned |
Bug 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/
* To test the fix manually:
1. Mark a package upgradable from the -security pocket as held, then run unattended-
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.
tags: | added: id-5ca50c3568756c4a351b6f5f |
Changed in unattended-upgrades (Ubuntu): | |
status: | New → Confirmed |
Changed in unattended-upgrades (Ubuntu Bionic): | |
status: | New → Confirmed |
Changed in unattended-upgrades (Ubuntu Disco): | |
status: | New → Confirmed |
description: | updated |
https:/ /github. com/mvo5/ unattended- upgrades/ pull/200