subscription-manager release --set=$VAR don't work as expected

[DirectorSloan]

Summary

I want to use the release pinning in ansible. Target systems are already registered successfully with the same module.

---

If I can provide any more information to help, please let me know.

Issue Type

Bug Report

Component Name

community.general.redhat_subscription

Ansible Version

Environment:

ansible-host ~/ansible-lab $ ansible --version
ansible [core 2.17.4]
  config file = /home/user/ansible-gpfs-lab/ansible.cfg
  configured module search path = ['/home/user/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /home/user/venv-ansible/lib/python3.12/site-packages/ansible
  ansible collection location = /home/user/.ansible/collections:/usr/share/ansible/collections
  executable location = /home/ben/venv-ansible/bin/ansible
  python version = 3.12.8 (main, Jan 29 2025, 08:30:51) [GCC 14.2.1 20241221] (/home/user/venv-ansible/bin/python)
  jinja version = 3.1.4
  libyaml = True

Community.general Version

$ ansible-galaxy collection list community.general
# /home/user/.ansible/collections/ansible_collections
Collection        Version
----------------- -------
community.general 10.3.0 

Configuration

$ ansible-config dump --only-changed
CONFIG_FILE() = None
EDITOR(env: EDITOR) = /bin/nano
PAGER(env: PAGER) = /usr/bin/less

OS / Environment

Subscription Manager stack on targets is the following (RHEL 9.4):

[user@ansible-host ~]# rpm -qa | grep -i subscription-manager
subscription-manager-rhsm-certificates-20220623-1.el9.noarch
libdnf-plugin-subscription-manager-1.29.40-1.el9.x86_64
python3-subscription-manager-rhsm-1.29.40-1.el9.x86_64
subscription-manager-1.29.40-1.el9.x86_64

Steps to Reproduce

- name: Pinning the os release if variable is set.
  community.general.redhat_subscription:
    release: "{{ redhat_subscription_manager_os_release }}"
  become: true
  when: redhat_subscription_manager_os_release is defined

Expected Results

changed

when no pinning is set or if pinning is set to another version (tested both).

Actual Results

returns green [ok] all the time.

Code of Conduct

• I agree to follow the Ansible Code of Conduct

[ansibullbot]

Files identified in the description:

• plugins/modules/redhat_subscription.py

If these files are incorrect, please update the component name section of the description or use the !component bot command.

click here for bot help

[ansibullbot]

cc @cnsnyder @ptoscano
click here for bot help

[ptoscano]

Is the system already registered? The module has historically done changes only when actually registering, and starting from community.general 6.5.0 it started to apply changes also when there was not a status change required (i.e. the system was not registered, and the execution would register the system).

For already registered systems, the module to be used is rhsm_release.