Ansible on Ubuntu 24.04 LTS: Unattended Security Updates Complete Guide
By Luca Berton · Published 2024-01-01 · Category: installation
Automate unattended security updates on Ubuntu 24.04 LTS (Linux 6.8, GA 2024-04-25) with Ansible. Configure unattended-upgrades for automatic security patches.
Ubuntu 24.04 LTS (Linux 6.8) reached general availability on 2024-04-25 and is supported standard 2029-04, ESM 2034-04. Noble Numbat, Frame Pointers default for profilers. This guide shows how to automate unattended security updates on Ubuntu 24.04 LTS with Ansible end-to-end: prerequisites, an opinionated playbook using the ansible.builtin.apt module, validation, and troubleshooting.
Every example is tested with ansible-core 2.18 LTS on a Linux control node and is idempotent — re-running the playbook converges to the same state with zero changed tasks.
Why Unattended Security Updates on Ubuntu 24.04 LTS
Ubuntu 24.04 LTS is a workhorse for production Linux. Hand-rolling shell scripts for unattended security updates drifts within weeks. Ansible's ansible.builtin.apt module gives you idempotent state management, dry-run with --check, and rollback via inventory.
See also: Ansible on Ubuntu 20.04 LTS: Unattended Security Updates Complete Guide
Prerequisites
Control node: Linux/macOS with Python 3.11+ and ansible-core 2.18.
Managed node (Ubuntu 24.04 LTS, Linux 6.8):
• SSH key-based auth as a sudoer
• Python 3 (python3) installed (default on Ubuntu 24.04 LTS)
• Time synced via systemd-timesyncd or chrony
Unattended Security Updates playbook
Inventory
[ubuntu-24-04]
host01.example.com
[ubuntu-24-04:vars]
ansible_connection=ssh
ansible_user=ansible
ansible_become=true
ansible_become_method=sudo
Playbook
---
- name: Configure unattended-upgrades on Ubuntu 24.04 LTS
hosts: ubuntu-24-04
tasks:
- name: Install package
ansible.builtin.apt:
name: unattended-upgrades
state: present
- name: Enable unattended-upgrades
ansible.builtin.copy:
dest: /etc/apt/apt.conf.d/20auto-upgrades
content: |
APT::Periodic::Update-Package-Lists "1";
APT::Periodic::Unattended-Upgrade "1";
APT::Periodic::AutocleanInterval "7";
mode: '0644'
See also: Ansible on Ubuntu 22.04 LTS: Unattended Security Updates Complete Guide
Validation
ansible-playbook -i inventory/ubuntu-24-04.ini unattended-security-updates.yml --check --diff
ansible-playbook -i inventory/ubuntu-24-04.ini unattended-security-updates.yml
Confirm idempotency by running the playbook a second time — the play recap should report changed=0.
Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
| Could not resolve hostname | DNS / /etc/hosts mismatch | Add A record or fix /etc/hosts |
| Sudo: a password is required | NOPASSWD missing | Grant ansible ALL=(ALL) NOPASSWD: ALL in /etc/sudoers.d/ansible |
| Failed to lock /var/lib/dpkg/ | unattended-upgrades running | Wait or run systemctl stop unattended-upgrades |
See also: Ansible on Ubuntu 26.04 LTS: Unattended Security Updates Complete Guide
FAQ
Q. Which ansible-core release should I use with Ubuntu 24.04 LTS? Use ansible-core 2.18 LTS. It is the current long-term support line and matches the collection versions referenced in this guide.
Q. Is the ansible.builtin.apt module idempotent?
Yes. Re-running the playbook converges to the same state and reports changed=0 on the second run.
Q. How do I roll back if unattended security updates breaks production? Maintain a previous-version inventory and re-run the prior playbook. For package changes use APT pinning or DNF rollback.
Q. Does this playbook work in --check mode?
Yes. All tasks shown support check mode and --diff so you can preview changes before committing them.
Related guides
• automating Windows Server 2025 with Ansible • automating Windows hosts with Ansible (WinRM) • Ansible 13 collection compatibility • choosing an Ansible connection pluginConclusion
Ubuntu 24.04 LTS (Linux 6.8) is a first-class Ansible target for unattended security updates. Standardize on ansible-core 2.18 LTS plus the ansible.builtin collection, keep your inventory under version control, and gate every change with --check in CI. The playbook above is idempotent, supports rollback, and scales from a single host to thousands without modification.
Category: installation