Seemingly randon execution time of unattended-upgrades
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| unattended-upgrades (Ubuntu) |
Confirmed
|
Low
|
Unassigned | ||
Bug Description
On Ubuntu 16.04 the execution time of unattended-upgrades is apparently defined by systemd timers and not cron anymore.
This seems to be a major change from other LTS distros which I see two issues with:
1) All the documentation online never mentions the change to systemd, therefore making the troubleshooting more complicated cause one would look in the wrong places.
2) The execution time is set to 6am and 6pm with a random delay of 12h. This is different than the settings for init.d systems where the timing is handled by cron (6am plus a random delay of 30 minutes).
It would probably make sense to change the systemd timer to reflect the same settings as the cron timer, and to mention in the documentation that the execution of unattended-upgrades is handled differently based on what system it is running on.
| Brian Murray (brian-murray) wrote | #1 |
| Changed in unattended-upgrades (Ubuntu): | |
| status: | New → Confirmed |
| tags: | added: xenial yakkety |
| Changed in unattended-upgrades (Ubuntu): | |
| importance: | Undecided → Low |
See /etc/cron.