RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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.
Bug 2143816 - ha_cluster - use no_log in tasks looping over pot. secret parameters
Summary: ha_cluster - use no_log in tasks looping over pot. secret parameters
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: rhel-system-roles
Version: 9.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 9.2
Assignee: Rich Megginson
QA Contact: michal novacek
Steven J. Levine
URL:
Whiteboard: role:ha_cluster
Depends On: 1803995 2127497
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-11-18 00:13 UTC by Rich Megginson
Modified: 2023-05-09 08:42 UTC (History)
7 users (show)

Fixed In Version: rhel-system-roles-1.21.0-0.14.el9
Doc Type: Bug Fix
Doc Text:
.The `ha_cluster` System Role logs no longer display unencrypted passwords and secrets The `ha_cluster` System Role accepts parameters that can be passwords or other secrets. Previously, some of the tasks would log their inputs and outputs. As a result, the role logs could contain unencrypted passwords and other secrets. With this update, the tasks have been changed to use the Ansible `no_log: true` directive and the task output is no longer displayed in the role logs. The `ha_cluster` System Role logs no longer contain passwords and other secrets. While this update protects secure information, the role logs now provide less information that you can use when debugging your configuration.
Clone Of: 2127497
Environment:
Last Closed: 2023-05-09 07:38:23 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-139873 0 None None None 2022-11-18 00:25:14 UTC
Red Hat Product Errata RHEA-2023:2246 0 None None None 2023-05-09 07:38:47 UTC

Comment 20 michal novacek 2023-02-20 08:20:41 UTC 
I have verified that no secret parameters are leaked from the role secrets. 

This have been verified by setting known plaintext secret and setting maximum
verbosity. Running all rhel-system-roles and regression playbooks did not leak
that secret to the log or standard output.
Comment 24 errata-xmlrpc 2023-05-09 07:38:23 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (rhel-system-roles bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2023:2246
Note You need to log in before you can comment on or make changes to this bug.