Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

Overriding boolean variables imported from ansible roles does not seem to work when running ansible roles.

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

How reproducible:
Always

Steps to Reproduce:
1. Import a role having boolean value true/false in defaults. example flag: true
2. Import the variables and override variable value. Example override flag to false
3. Assign the role to a host and run roles and notice the value is not overridden

For all non boolean overridden variables, the overridden value can be seen in dynflow task details under ansible_inventory json. But the boolean overridden variables never reach there and hence never makes to role execution.

Expected results:

Boolean vars overriding should work as other types work

Additional info:

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