Ansible on Fedora 43: Firewalld Zone Configuration Complete Guide
By Luca Berton · Published 2024-01-01 · Category: installation
Automate firewalld zone configuration on Fedora 43 (Linux 6.10, GNOME 46, GA 2024-10-29) with Ansible.
Fedora 43 (Linux 6.10, GNOME 46) reached general availability on 2024-10-29 and is supported ~2025-11. DNF5 default, RPM 4.20. This guide shows how to automate firewalld zone configuration on Fedora 43 with Ansible end-to-end: prerequisites, an opinionated playbook using the ansible.posix.firewalld 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 Firewalld Zone Configuration on Fedora 43
Fedora 43 is a workhorse for production Linux. Hand-rolling shell scripts for firewalld zone configuration drifts within weeks. Ansible's ansible.posix.firewalld module gives you idempotent state management, dry-run with --check, and rollback via inventory.
See also: Ansible on Fedora 44: Firewalld Zone Configuration Complete Guide
Prerequisites
Control node: Linux/macOS with Python 3.11+ and ansible-core 2.18.
Managed node (Fedora 43, Linux 6.10, GNOME 46):
• SSH key-based auth as a sudoer
• Python 3 (python3) installed (default on Fedora 43)
• Time synced via systemd-timesyncd or chrony
Firewalld Zone Configuration playbook
Inventory
[fedora-43]
host01.example.com
[fedora-43:vars]
ansible_connection=ssh
ansible_user=ansible
ansible_become=true
ansible_become_method=sudo
Playbook
---
- name: firewalld on Fedora 43
hosts: fedora-43
tasks:
- name: Default zone public
ansible.posix.firewalld:
zone: public
state: present
permanent: true
- name: Allow https
ansible.posix.firewalld:
service: https
zone: public
state: enabled
permanent: true
immediate: true
- name: Rich rule rate-limit ssh
ansible.posix.firewalld:
rich_rule: 'rule service name="ssh" accept limit value="3/m"'
zone: public
state: enabled
permanent: true
immediate: true
See also: Ansible on Fedora 45: Firewalld Zone Configuration Complete Guide
Validation
ansible-playbook -i inventory/fedora-43.ini firewalld-zone-configuration.yml --check --diff
ansible-playbook -i inventory/fedora-43.ini firewalld-zone-configuration.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 Fedora 46: Firewalld Zone Configuration Complete Guide
FAQ
Q. Which ansible-core release should I use with Fedora 43? 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.posix.firewalld 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 firewalld zone configuration 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
• PSRP and OpenSSH on Windows Server 2025 via Ansible • Ansible WinRM connection setup • how to migrate to ansible-core 2.20 • Ansible network connection pluginsConclusion
Fedora 43 (Linux 6.10, GNOME 46) is a first-class Ansible target for firewalld zone configuration. Standardize on ansible-core 2.18 LTS plus the ansible.posix 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