Bug 2009849 - BMC credentials could be logged if they change
Summary: BMC credentials could be logged if they change
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Bare Metal Hardware Provisioning
Version: 4.9
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.9.z
Assignee: Zane Bitter
QA Contact: Lubov
URL:
Whiteboard:
Depends On: 2004625
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-10-01 19:02 UTC by Zane Bitter
Modified: 2021-11-10 21:02 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2004625
Environment:
Last Closed: 2021-11-10 21:02:21 UTC
Target Upstream Version:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift baremetal-operator pull 183 0 None open [release-4.9] Bug 2009849: Avoid logging BMC password when creds change 2021-10-15 19:14:11 UTC
Red Hat Product Errata RHBA-2021:4119 0 None None None 2021-11-10 21:02:32 UTC

Description Zane Bitter 2021-10-01 19:02:31 UTC 
+++ This bug was initially created as a clone of Bug #2004625 +++

Beginning with 4.9, if the user changes the credentials for a BaremetalHost (by editing or changing the Secret that contains them), the baremetal operator may log the new credentials in the process of updating them in Ironic.

This is a very rare event as users don't generally change the BMC credentials, but it should be avoided.
Comment 4 Lubov 2021-11-02 13:25:33 UTC 
verified on 4.9.0-0.nightly-2021-11-02-033840
Comment 7 errata-xmlrpc 2021-11-10 21:02:21 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 (OpenShift Container Platform 4.9.6 bug fix 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/RHBA-2021:4119
Note You need to log in before you can comment on or make changes to this bug.