Bug 1948787

Summary:	secret.StringData shouldn't be used for reads
Product:	OpenShift Container Platform	Reporter:	Stephen Benjamin <stbenjam>
Component:	Bare Metal Hardware Provisioning	Assignee:	Angus Salkeld <asalkeld>
Bare Metal Hardware Provisioning sub component:	cluster-baremetal-operator	QA Contact:	Amit Ugol <augol>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	high
Priority:	urgent	CC:	aos-bugs, asalkeld, rbartal
Version:	4.8	Keywords:	Triaged
Target Milestone:	---
Target Release:	4.8.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Cause: a write only field was used to determine if data was present. Consequence: This lead to continuous (unnecessary) secret updates. Fix: secret.Data was used instead. Result: no unnecessary secret updates.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-07-27 22:59:54 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 Stephen Benjamin 2021-04-12 22:21:33 UTC

CBO is making a high number of requests on a full e2e run, upwards of 100K -- mostly gets requests. This appears to be due to using secret.StringData for reads.

Comment 4 errata-xmlrpc 2021-07-27 22:59:54 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 (Moderate: OpenShift Container Platform 4.8.2 bug fix and security 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/RHSA-2021:2438