Ansible on Ubuntu 26.04 LTS: AppArmor Profile Management Complete Guide

Ubuntu 26.04 LTS (Linux 6.14) reached general availability on 2026-04-23 and is supported standard 2031-04, ESM 2036-04. Stonking Stingray, sudo-rs default, APT rollback, Wayland-only desktop. This guide shows how to automate apparmor profile management on Ubuntu 26.04 LTS with Ansible end-to-end: prerequisites, an opinionated playbook using the community.general.apparmor 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 AppArmor Profile Management on Ubuntu 26.04 LTS

Ubuntu 26.04 LTS is a workhorse for production Linux. Hand-rolling shell scripts for apparmor profile management drifts within weeks. Ansible's community.general.apparmor module gives you idempotent state management, dry-run with --check, and rollback via inventory.

See also: Ansible on Ubuntu 20.04 LTS: AppArmor Profile Management Complete Guide

Prerequisites

Control node: Linux/macOS with Python 3.11+ and ansible-core 2.18.

Managed node (Ubuntu 26.04 LTS, Linux 6.14): • SSH key-based auth as a sudoer • Python 3 (python3) installed (default on Ubuntu 26.04 LTS) • Time synced via systemd-timesyncd or chrony

AppArmor Profile Management playbook

Inventory

[ubuntu-26-04]
host01.example.com
[ubuntu-26-04:vars]
ansible_connection=ssh
ansible_user=ansible
ansible_become=true
ansible_become_method=sudo

Playbook

---
- name: AppArmor enforcement on Ubuntu 26.04 LTS
  hosts: ubuntu-26-04
  tasks:
    - name: Ensure apparmor utilities present
      ansible.builtin.apt:
        name: [apparmor, apparmor-utils]
        state: present
    - name: Enforce nginx profile
      community.general.apparmor:
        name: usr.sbin.nginx
        state: enforce

See also: Ansible on Ubuntu 22.04 LTS: AppArmor Profile Management Complete Guide

Validation

ansible-playbook -i inventory/ubuntu-26-04.ini apparmor-profile-management.yml --check --diff
ansible-playbook -i inventory/ubuntu-26-04.ini apparmor-profile-management.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 24.04 LTS: AppArmor Profile Management Complete Guide

FAQ

Q. Which ansible-core release should I use with Ubuntu 26.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 community.general.apparmor 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 apparmor profile management 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

• Ansible Windows Server 2025 automation complete guide • Windows automation over WinRM with Ansible • planning an Ansible 13 upgrade • SSH vs WinRM vs Docker connections in Ansible

Conclusion

Ubuntu 26.04 LTS (Linux 6.14) is a first-class Ansible target for apparmor profile management. Standardize on ansible-core 2.18 LTS plus the community.general 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.