Bug 2254503

Summary: Ansible variables that are flagged as hidden values are shown with the ansible variables on the host level.
Product: Red Hat Satellite Reporter: mithun kalyat <mkalyat>
Component: Ansible - Configuration ManagementAssignee: Girija Soni <gisoni>
Status: CLOSED MIGRATED QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.14.0CC: gisoni, nalfassi, rlavi, ybuenos
Target Milestone: UnspecifiedKeywords: MigratedToJIRA, Triaged, WeaknessTracking
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: 2024-06-06 16:38:20 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 mithun kalyat 2023-12-14 09:24:40 UTC
Description of problem:

Ansible variables are marked as hidden values in the satellite webUI, but the same is visible when the role or variable is added to the host.

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

Satellite 6.14

Steps to Reproduce:

1. Import the role or variable and override the default value. Check the 'Hidden Value' box so that the 'Default value' will become hidden.

    Configure --> Variables --> sample_variable --> Default Behavior

2. Import the role/variable on the host.

    Hosts --> All hosts --> host.example.com --> Ansible -> Variables --> sample_variable 

The 'Hidden value' is visible as plain text.

Actual results:

The 'Hidden Value' is visible as plain text on host level.

Expected results:

'Hidden Value' should be hidden.

Comment 6 Eric Helms 2024-06-06 16:38:20 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.