Ubuntu
unattended-upgrades package

  1. Xenial (16.04)
  2. Bug #1686470
  3. Comment #25

Comment 25 for bug 1686470

Revision history for this message
Dimitri John Ledkov (xnox) wrote :

Similarly starting a zesty container for the same test case:
ii apt 1.4 amd64

upgrading to:
ii apt 1.4.6~17.04.1 amd64

Setting up apt (1.4.6~17.04.1) ...
Created symlink /etc/systemd/system/timers.target.wants/apt-daily-upgrade.timer → /lib/systemd/system/apt-daily-upgrade.timer.

However, this unit did not get activated.
# systemctl status apt-daily-upgrade.timer
● apt-daily-upgrade.timer - Daily apt upgrade and clean activities
   Loaded: loaded (/lib/systemd/system/apt-daily-upgrade.timer; enabled; vendor preset: enabled)
   Active: inactive (dead)

After rebooting the unit is active:
# systemctl list-timers
NEXT LEFT LAST PASSED UNIT ACTIVATES
Fri 2017-07-28 09:55:34 UTC 14min left n/a n/a systemd-tmpfiles-clean.timer systemd-tmpfiles-clean.service
Fri 2017-07-28 10:32:53 UTC 52min left Fri 2017-07-28 09:36:24 UTC 4min 22s ago motd-news.timer motd-news.service
Fri 2017-07-28 13:44:26 UTC 4h 3min left Fri 2017-07-28 09:36:24 UTC 4min 22s ago snapd.refresh.timer snapd.refresh.service
Fri 2017-07-28 18:04:19 UTC 8h left Fri 2017-07-28 09:36:24 UTC 4min 22s ago apt-daily.timer apt-daily.service
Sat 2017-07-29 06:52:52 UTC 21h left n/a n/a apt-daily-upgrade.timer apt-daily-upgrade.service

I will leave this zesty instance running, but it may mean a fix up on zesty is needed to activate the apt-daily-upgrade.timer in postinst.