Ansible on Fedora 46: Cockpit Web Console Provisioning Complete Guide

Fedora 46 (Linux 6.14, GNOME 48) reached general availability on 2026-04-21 and is supported ~2027-05. Default user namespaces, GCC 15. This guide shows how to automate cockpit web console provisioning on Fedora 46 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 Cockpit Web Console Provisioning on Fedora 46

Fedora 46 is a workhorse for production Linux. Hand-rolling shell scripts for cockpit web console provisioning 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 Fedora 43: Cockpit Web Console Provisioning Complete Guide

Prerequisites

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

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

Cockpit Web Console Provisioning playbook

Inventory

[fedora-46]
host01.example.com
[fedora-46:vars]
ansible_connection=ssh
ansible_user=ansible
ansible_become=true
ansible_become_method=sudo

Playbook

---
- name: Cockpit on Fedora 46
  hosts: fedora-46
  tasks:
    - name: Install cockpit
      ansible.builtin.dnf:
        name: [cockpit, cockpit-storaged, cockpit-pcp]
        state: present
    - name: Enable socket
      ansible.builtin.systemd_service:
        name: cockpit.socket
        enabled: true
        state: started
    - name: Open firewall
      ansible.posix.firewalld:
        service: cockpit
        permanent: true
        immediate: true
        state: enabled

See also: Ansible on Fedora 44: Cockpit Web Console Provisioning Complete Guide

Validation

ansible-playbook -i inventory/fedora-46.ini cockpit-web-console-provisioning.yml --check --diff
ansible-playbook -i inventory/fedora-46.ini cockpit-web-console-provisioning.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 45: Cockpit Web Console Provisioning Complete Guide

FAQ

Q. Which ansible-core release should I use with Fedora 46? 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 cockpit web console provisioning 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

• configuring Windows Server 2025 hosts with Ansible • Kerberos and NTLM authentication for Ansible WinRM • Ansible 13 breaking-changes reference • when to use local vs SSH in Ansible

Conclusion

Fedora 46 (Linux 6.14, GNOME 48) is a first-class Ansible target for cockpit web console provisioning. 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.