Bug 1889403

Summary:	Some OLM events hide the underlying errors
Product:	OpenShift Container Platform	Reporter:	OpenShift BugZilla Robot <openshift-bugzilla-robot>
Component:	OLM	Assignee:	Evan Cordell <ecordell>
OLM sub component:	OLM	QA Contact:	kuiwang
Status:	CLOSED WONTFIX	Docs Contact:
Severity:	low
Priority:	low	CC:	krizza, nhale, vdinh
Version:	4.6	Keywords:	Reopened
Target Milestone:	---
Target Release:	4.6.z
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:	2021-02-05 14:46:51 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1885403
Bug Blocks:

Description OpenShift BugZilla Robot 2020-10-19 15:25:29 UTC

+++ This bug was initially created as a clone of Bug #1885403 +++

Description of problem:
Some OLM events do not expose the underlying error leading to lesser debug capabilities.


Additional info:
Please see https://github.com/operator-framework/operator-lifecycle-manager/blob/master/pkg/controller/operators/olm/operator.go#L1535

It is only an example, there are several occurrences of the same issue.
It can be seen the actual error is not exposed.

Comment 4 Kevin Rizza 2021-02-05 14:35:15 UTC

I'm closing this bug as WONTFIX. The expected backport process of OpenShift ensures that a bug with a priority of LOW will assuredly never actually make the cut for the list of bzs to backport.