Bug 1805560 - Imported Boolean Ansible variables breaks all other ansible variables for a host
Summary: Imported Boolean Ansible variables breaks all other ansible variables for a host
Keywords:
Status: CLOSED DUPLICATE of bug 1785231
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Ansible
Version: 6.6.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Lukas Pramuk
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-02-21 02:17 UTC by Alexey Masolov
Modified: 2023-03-24 17:02 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-02-23 23:04:04 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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 ***


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