Ansible on Oracle Linux 9.5: DNF Module Streams Complete Guide

Oracle Linux 9.5 (Linux 5.14 / UEK 7) reached general availability on 2024-12 and is supported with RHEL 9.5. UEK kernel option; Ksplice live patching. This guide shows how to automate dnf module streams on Oracle Linux 9.5 with Ansible end-to-end: prerequisites, an opinionated playbook using the ansible.builtin.dnf 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 DNF Module Streams on Oracle Linux 9.5

Oracle Linux 9.5 is a workhorse for production Linux. Hand-rolling shell scripts for dnf module streams drifts within weeks. Ansible's ansible.builtin.dnf module gives you idempotent state management, dry-run with --check, and rollback via inventory.

See also: Ansible on AlmaLinux 9.5: DNF Module Streams Complete Guide

Prerequisites

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

Managed node (Oracle Linux 9.5, Linux 5.14 / UEK 7): • SSH key-based auth as a sudoer • Python 3 (python3) installed (default on Oracle Linux 9.5) • Time synced via systemd-timesyncd or chrony

DNF Module Streams playbook

Inventory

[oracle-linux-9-5]
host01.example.com
[oracle-linux-9-5:vars]
ansible_connection=ssh
ansible_user=ansible
ansible_become=true
ansible_become_method=sudo

Playbook

---
- name: DNF module streams on Oracle Linux 9.5
  hosts: oracle-linux-9-5
  tasks:
    - name: Reset nodejs module
      ansible.builtin.command: dnf module reset -y nodejs
      changed_when: true
    - name: Enable nodejs:20 stream
      ansible.builtin.command: dnf module enable -y nodejs:20
      changed_when: true
    - name: Install nodejs from stream
      ansible.builtin.dnf:
        name: '@nodejs:20/development'
        state: present

See also: Ansible on Red Hat Enterprise Linux 8.10: DNF Module Streams Complete Guide

Validation

ansible-playbook -i inventory/oracle-linux-9-5.ini dnf-module-streams.yml --check --diff
ansible-playbook -i inventory/oracle-linux-9-5.ini dnf-module-streams.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 Red Hat Enterprise Linux 9.4: DNF Module Streams Complete Guide

FAQ

Q. Which ansible-core release should I use with Oracle Linux 9.5? 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.dnf 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 dnf module streams 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

• Windows Server 2025 baseline with Ansible • Windows automation over WinRM with Ansible • Ansible 13 release notes overview • Ansible connection types: SSH, WinRM, Local, Docker, Network guide

Conclusion

Oracle Linux 9.5 (Linux 5.14 / UEK 7) is a first-class Ansible target for dnf module streams. 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.