osism / issues

This repository is used for bug reports that are cross-project or not bound to a specific repository (or to an unknown repository).
https://www.osism.tech
1 stars 1 forks source link

disable unattended-updates #614

Closed schulze-b1 closed 10 months ago

schulze-b1 commented 1 year ago

i saw in apt logs that there are unattended-updates being installed nightly. this program comes from the pre-installed package unattended-updates. we do not want this in an enterprise environment that there are updates installed without our knowledge and action. what is the osism way to disable this on all our ubuntu hosts?

berendt commented 1 year ago

Run the cleanup role. The role includes a task that uninstalls the unattended-upgrades package.

https://github.com/osism/ansible-collection-commons/blob/main/roles/cleanup/tasks/packages-Debian.yml#L19-L25

schulze-b1 commented 1 year ago

is this anywhere documented? i couldn't find anything related to the cleanup role in https://docs.osism.tech/appendix/commands.html or the docs in general.

berendt commented 1 year ago

The append is out of date. Run osism apply. This will print out a table of all available commands on a manager.

fkr commented 1 year ago

@berendt Would it make sense to document steps like these as ‘typical post-install steps’?

berendt commented 1 year ago

The cleanup role is already part of the bootstrap playbook:

https://github.com/osism/ansible-playbooks/blob/main/playbooks/generic/bootstrap.yml#L64

As well as the maintenance playbook:

https://github.com/osism/ansible-playbooks/blob/main/playbooks/generic/maintenance.yml#L84

Both plays are the preferred way to do the bootstrap/maintenance. Not sure if it makes sense to document post-install tasks that are already part of the standard procedure.

fkr commented 1 year ago

@schulze-b1 if this is ‘standard procedure’ already - what could’ve improved the situation for you to be aware of ‘this standard procedure’?

berendt commented 10 months ago

Stale. Please re-open if required.