Ansible on Rocky Linux 9.5: Subscription Manager Registration Complete Guide

Rocky Linux 9.5 (Linux 5.14) reached general availability on 2024-11-19 and is supported with RHEL 9.5. CIQ-backed RHEL rebuild; Peridot build system. This guide shows how to automate subscription manager registration on Rocky Linux 9.5 with Ansible end-to-end: prerequisites, an opinionated playbook using the community.general.redhat_subscription 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 Subscription Manager Registration on Rocky Linux 9.5

Rocky Linux 9.5 is a workhorse for production Linux. Hand-rolling shell scripts for subscription manager registration drifts within weeks. Ansible's community.general.redhat_subscription module gives you idempotent state management, dry-run with --check, and rollback via inventory.

See also: Ansible on AlmaLinux 9.5: Subscription Manager Registration Complete Guide

Prerequisites

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

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

Subscription Manager Registration playbook

Inventory

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

Playbook

---
- name: Register Rocky Linux 9.5 with RHSM
  hosts: rocky-linux-9-5
  tasks:
    - name: Register and auto-attach
      community.general.redhat_subscription:
        state: present
        username: '{{ vault_rhsm_user }}'
        password: '{{ vault_rhsm_password }}'
        auto_attach: true
        force_register: false
    - name: Enable required repos
      community.general.rhsm_repository:
        name:
          - rhel-9-for-x86_64-baseos-rpms
          - rhel-9-for-x86_64-appstream-rpms
        state: enabled

See also: Ansible on Oracle Linux 9.5: Subscription Manager Registration Complete Guide

Validation

ansible-playbook -i inventory/rocky-linux-9-5.ini subscription-manager-registration.yml --check --diff
ansible-playbook -i inventory/rocky-linux-9-5.ini subscription-manager-registration.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 8.10: Subscription Manager Registration Complete Guide

FAQ

Q. Which ansible-core release should I use with Rocky 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 community.general.redhat_subscription 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 subscription manager registration 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 • Ansible connection types: SSH, WinRM, Local, Docker, Network guide

Conclusion

Rocky Linux 9.5 (Linux 5.14) is a first-class Ansible target for subscription manager registration. 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.