Enable unattended-upgrades #598
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "bugfix/499-unattended_upgrades"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
We were missing a positive value on
["apt"]["unattended_upgrades"]["enable"]
to enable it.This is running on akkounts-1, I have executed
unattended-upgrades --dry-run
after a Chef run. Now we can wait for the actual run tomorrow.closes #499
@greg Did it run OK?
It ran successfully but we did not get email notifications, I'm looking into it before we can merge it
OK I got it, I had forgotten to run Chef again after fixing the config to send email notifications. So the next upgrade should send us an email now
I checked again, found an issue that prevented the emails from being sent. I fixed what should be the last issue, now we should get emails next time there's a package upgrade on akkounts-1
Any emails yet? 🤔
There hasn't been any package update since I fixed the email config, I'll keep checking
I fixed the issue that was preventing updates from installing in
cc40c0db19
(because the Ubuntu version running on akkounts-1 needs ESM). I also ran into an issue with the postfix config, due to an old issue in the Chef cookbook. I forked it to our Gitea and also created a PR upstream: https://github.com/sous-chefs/postfix/pull/213Unattended upgrades have been installed on akkounts-1, next I'll resend the email, since the postfix config was still broken when the first successful upgrade ran
Resent the failed email notification and created an email rule so the next one should arrive in the right folder, I think this one should be good to review
This morning an unattended upgrade was performed on akkounts-1, and the email was sent and filtered to the right folder.
Great!