Enable unattended-upgrades #598
Labels
Clear labels
monitoring
bug
design
dev environment
docs
duplicate
enhancement
feature
good first issue
idea
invalid
kredits-1
kredits-2
kredits-3
on hold
ops
question
security
ui/ux
wontfix
service
discourse
Kosmos Community Forums
Infrastructure metrics, alerts, notifications, etc.
service
accounts
Kosmos Accounts
service
drone-ci
Kosmos Drone CI
service
email
mail.kosmos.org
service
garage
S3-compatible object storage
service
gitea
Kosmos Gitea
service
ipfs
Kosmos IPFS
service
mastodon
kosmos.social
service
nostr
Relays, Blossom server, etc.
service
postgres
Database cluster
service
remotestorage
Portable data storage for the Web
service
wiki
Kosmos Wiki
service
xmpp
Kosmos Chat
Something is not working
Graphic/visual design
Config, builds, CI, deployment, etc.
Documentation
This issue or pull request already exists
Improving existing functionality
New functionality
Dive in, and start contributing
Something to consider
Not a bug
Small contribution
Medium contribution
Large contribution
Currently not actionable
Manual IT ops activities
Looking for an answer
release
major
release
minor
release
patch
All your base are belong to us
User interface, process design, etc.
This won't be fixed
Milestone
No items
No Milestone
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: kosmos/chef#598
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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-runafter 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!