Bug 1860611 - [RFE]Overriding Ansible variable with Host Parameter
Summary: [RFE]Overriding Ansible variable with Host Parameter
Keywords:
Status: CLOSED DUPLICATE of bug 1744521
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Ansible - Configuration Management
Version: 6.8.0
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Lukas Pramuk
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-07-25 17:55 UTC by rakesh kumar
Modified: 2023-10-06 21:15 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-08-24 11:09:18 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description rakesh kumar 2020-07-25 17:55:51 UTC
Description of problem:
Overriding an Ansible Variable using a Host Parameter or Host Group Parameter does not work, ansible picks up the default value of the variable from the role even though the parameter is overridden and have a new value defined through host parameter.


Version-Release number of selected component (if applicable):
6.8/6.7

How reproducible:
Always

Steps to Reproduce:
1. Import a role on Satellite which has a parameter which can be overridden
2. Attach that role to the client
3. Override the parameter in configure -> Ansible -> Variable -> click on variable -> check on `override` under 'Default Behavior' section
4. Now, go to the client, create a host parameter with the same name, select the parameter type and provide new value of the parameter.
5. Run the role and check the output to know the value which ansible picked

Actual results:
Ansible picking the default value from the role


Expected results:
Should pick the new value from the host parameter


Additional info:

If we create a matcher in the variable using the fqdn for the host, then it works fine.

Comment 3 Tomer Brisker 2020-08-24 11:09:18 UTC

*** This bug has been marked as a duplicate of bug 1744521 ***


Note You need to log in before you can comment on or make changes to this bug.