Bug 1744521 - There is no way to identify the overriden Ansible variables while creating or editing an existing host
Summary: There is no way to identify the overriden Ansible variables while creating or...
Keywords:
Status: NEW
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Ansible
Version: 6.6.0
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: Unspecified
Assignee: Ondřej Pražák
QA Contact: Lukas Pramuk
URL:
Whiteboard:
: 1860611 1866830 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-22 10:21 UTC by Mihir Lele
Modified: 2021-04-27 19:40 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 25159 0 Normal Ready For Testing Ansible variables overrides on hosts/edit page 2021-02-16 06:53:04 UTC

Description Mihir Lele 2019-08-22 10:21:57 UTC
Description of problem:

There is no way to identify the overridden Ansible variables while creating or editing an existing host. Satellite also does not provide the option to override the overridden variables like it does with puppet. If any puppet class is overridden with a value, then it is visible under "Puppet class parameters" and also provides an option to override the value while creating a new host. This option seems to be absent with the Ansible variables.

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


How reproducible: Always


Steps to Reproduce:
1.  Override a Ansible variable for a Ansible role.
2.  Then try creating a new host and associate the Ansible role with the host and you will never know that some of the variables are overridden unless you go to the Ansible variables page.

Comment 3 Ondřej Pražák 2019-11-18 14:59:11 UTC
Connecting redmine issue https://projects.theforeman.org/issues/25159 from this bug

Comment 4 Tomer Brisker 2020-08-24 10:56:07 UTC
*** Bug 1866830 has been marked as a duplicate of this bug. ***

Comment 5 Tomer Brisker 2020-08-24 11:09:19 UTC
*** Bug 1860611 has been marked as a duplicate of this bug. ***

Comment 7 Sean O'Keeffe 2020-12-09 14:45:19 UTC
*** Bug 1871180 has been marked as a duplicate of this bug. ***


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