Comment 24 for bug 1686470

Starting with:
ii apt 1.2.20 amd64 commandline package manager

The following timers are present:
# systemctl list-timers
NEXT LEFT LAST PASSED UNIT ACTIVATES
Fri 2017-07-28 09:42:31 UTC 14min left n/a n/a systemd-tmpfiles-clean.timer systemd-tmpfiles-clean.service
Fri 2017-07-28 12:52:15 UTC 3h 24min left n/a n/a snapd.refresh.timer snapd.refresh.service
Sat 2017-07-29 03:09:15 UTC 17h left n/a n/a apt-daily.timer apt-daily.service

The apt-daily.service is going to run, unexpectadly, at 3:09am.

Upgrading just apt:
ii apt 1.2.24 amd64 commandline package manager

# systemctl list-timers
NEXT LEFT LAST PASSED UNIT ACTIVATES
Fri 2017-07-28 09:42:31 UTC 12min left n/a n/a systemd-tmpfiles-clean.timer systemd-tmpfiles-clean.service
Fri 2017-07-28 10:03:19 UTC 33min left n/a n/a snapd.refresh.timer snapd.refresh.service
Fri 2017-07-28 20:18:24 UTC 10h left Fri 2017-07-28 09:27:35 UTC 1min 57s ago apt-daily.timer apt-daily.service
Sat 2017-07-29 06:30:36 UTC 21h left n/a n/a apt-daily-upgrade.timer apt-daily-upgrade.service

Now there is timer to do a refresh at a random time, yet there is a predictable apt-daily-upgrade to apply the timer between 6 and 7am.

All of this looks good.

I will leave this container around, and will check if upgrades were applied tomorrow.