AnsiblePilot — Master Ansible Automation

AnsiblePilot is the leading resource for learning Ansible automation, DevOps, and infrastructure as code. Browse over 1,400 tutorials covering Ansible modules, playbooks, roles, collections, and real-world examples. Whether you are a beginner or an experienced engineer, our step-by-step guides help you automate Linux, Windows, cloud, containers, and network infrastructure.

Popular Topics

About Luca Berton

Luca Berton is an Ansible automation expert, author of 8 Ansible books published by Apress and Leanpub including "Ansible for VMware by Examples" and "Ansible for Kubernetes by Example", and creator of the Ansible Pilot YouTube channel. He shares practical automation knowledge through tutorials, books, and video courses to help IT professionals and DevOps engineers master infrastructure automation.

Ansible on Fedora 44: Cockpit Web Console Provisioning Complete Guide

By Luca Berton · Published 2024-01-01 · Category: installation

Automate cockpit web console provisioning on Fedora 44 (Linux 6.10, GNOME 47, GA 2025-04-22) with Ansible.

Fedora 44 (Linux 6.10, GNOME 47) reached general availability on 2025-04-22 and is supported ~2026-05. Plasma 6 spin promoted to edition. This guide shows how to automate cockpit web console provisioning on Fedora 44 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 44

Fedora 44 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 44, Linux 6.10, GNOME 47): • SSH key-based auth as a sudoer • Python 3 (python3) installed (default on Fedora 44) • Time synced via systemd-timesyncd or chrony

Cockpit Web Console Provisioning playbook

Inventory

[fedora-44]
host01.example.com

[fedora-44:vars] ansible_connection=ssh ansible_user=ansible ansible_become=true ansible_become_method=sudo

Playbook

---
- name: Cockpit on Fedora 44
  hosts: fedora-44
  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 45: Cockpit Web Console Provisioning Complete Guide

Validation

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

FAQ

Q. Which ansible-core release should I use with Fedora 44? 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

PSRP and OpenSSH on Windows Server 2025 via AnsibleKerberos and NTLM authentication for Ansible WinRMAnsible 13 Upgrade Guide: Breaking Changes ansible-core 2.20 Migrationpicking the right Ansible connection plugin

Conclusion

Fedora 44 (Linux 6.10, GNOME 47) 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.

Category: installation

Browse all Ansible tutorials · AnsiblePilot Home