Bug 1805560

Summary: Imported Boolean Ansible variables breaks all other ansible variables for a host
Product: Red Hat Satellite Reporter: Alexey Masolov <amasolov>
Component: Ansible - Configuration ManagementAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED DUPLICATE QA Contact: Lukas Pramuk <lpramuk>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.6.0CC: dsynk
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-02-23 23:04:04 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Alexey Masolov 2020-02-21 02:17:04 UTC 
Description of problem:
If there is an imported Boolean type ansible variable that overrides default value then all hosts with that role will have no ansible variables assigned. 

Version-Release number of selected component (if applicable):
Satellite 6.6.1

How reproducible:
100%

Steps to Reproduce:
1. Import a role with a boolean variable
2. Import that variable as boolean into Satellite and assign a new default value
3. Assign the role to a host
3. Run the role and see if the variable was used OR check YAML output for the host to see that there are no ansible variables assigned. If you do that with a string variable then it works.

Actual results:
Variables are missing from the YAML output and not accessible from the role

Expected results:
Works as with string variables

Additional info:
Comment 4 Alexey Masolov 2020-02-23 23:04:04 UTC 

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