-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
redhat_subscription: consumer_name is ignored #3486
Comments
Files identified in the description: If these files are incorrect, please update the |
Same here with red hat linux 8.5 tested |
Files identified in the description: If these files are incorrect, please update the |
Fixes ansible-collections#3486. From the man-pages of subscription-manager, none of the parameters used are tied to the activationkey except the two that remain in its else-clause. Note that type is not mentioned in the man-pages on 7.6 (at least), but is still present and available.
Hi folks, since the old PR (ansible/ansible#60266) that was done by @thor was IMHO good, I took the liberty of porting it to this repository (community.general): #5627 |
Fixes ansible-collections#3486. From the man-pages of subscription-manager, none of the parameters used are tied to the activationkey except the two that remain in its else-clause. Note that type is not mentioned in the man-pages on 7.6 (at least), but is still present and available.
Fixes ansible-collections#3486. From the man-pages of subscription-manager, none of the parameters used are tied to the activationkey except the two that remain in its else-clause. Note that type is not mentioned in the man-pages on 7.6 (at least), but is still present and available.
Fixes #3486. From the man-pages of subscription-manager, none of the parameters used are tied to the activationkey except the two that remain in its else-clause. Note that type is not mentioned in the man-pages on 7.6 (at least), but is still present and available. Co-authored-by: Thor K. H <[email protected]>
Fixes #3486. From the man-pages of subscription-manager, none of the parameters used are tied to the activationkey except the two that remain in its else-clause. Note that type is not mentioned in the man-pages on 7.6 (at least), but is still present and available. Co-authored-by: Thor K. H <[email protected]> (cherry picked from commit f7fa54e)
Fixes #3486. From the man-pages of subscription-manager, none of the parameters used are tied to the activationkey except the two that remain in its else-clause. Note that type is not mentioned in the man-pages on 7.6 (at least), but is still present and available. Co-authored-by: Thor K. H <[email protected]> (cherry picked from commit f7fa54e) Co-authored-by: Pino Toscano <[email protected]>
Summary
When using consumer_name to override name for foreman registration it is ignored during deployment redhat_subscription task: example below
this was reported in 2018 here: ansible/ansible#50502 but looks to be not fixed
example:
redhat_subscription:
org_id: "{{ foreman_default_organisation }}"
activationkey: "{{ foreman_activation_key }}"
consumer_name: "{{ foreman_register_consumer_hostname }}"
force_register: "{{ foreman_register_force | default('no') | bool }}"
auto_attach: yes
Issue Type
Bug Report
Component Name
redhat_subscription
Ansible Version
Community.general Version
Configuration
OS / Environment
CentOS 7 / OSX / Molecule testing
Steps to Reproduce
Expected Results
name in foreman should be different to hostname on server if consumer_name is overriden
Actual Results
hostname stays the same
Code of Conduct
The text was updated successfully, but these errors were encountered: