Bug 1972478

Summary:	OLM: Failure alert message for copied CSV not helpful
Product:	OpenShift Container Platform	Reporter:	OpenShift BugZilla Robot <openshift-bugzilla-robot>
Component:	Management Console	Assignee:	Robb Hamilton <rhamilto>
Status:	CLOSED ERRATA	QA Contact:	Yanping Zhang <yanpzhan>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.8	CC:	aos-bugs, jokerman, yanpzhan
Target Milestone:	---
Target Release:	4.8.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Cause: The UI shows `status.message` in the alert for failed CSVs, but it's not meaningful when the CSV is copied since it's always this generic message. Consequence: The generic message does not help the user troubleshoot the failed CSV. Fix: Change the behavior for copied CSVs to show a more meaningful message and include a link to the original CSV to troubleshoot. Result: The new message for copied CSVs informs the user to see the original CSV for the failure reason and provides a link to it.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-08-10 11:27:36 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:	1967658
Bug Blocks:

Description OpenShift BugZilla Robot 2021-06-16 02:53:06 UTC

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

Created attachment 1788853 [details]
Screenshot

Currently, `status.message` for a copied CSV is always

> The operator is running in openshift-operators but is managing this namespace

We show `status.message` in the alert for failed CSVs, but it's not meaningful when the CSV is copied since it's always this generic message. We should change the behavior for copied CSVs to show a more meaningful message (maybe with a link to the original CSV to troubleshoot?).

See attached screenshot

--- Additional comment from jhadvig on 2021-06-07 10:32:24 UTC ---

Wondering if we should not rather create a RFE story for this issue?

--- Additional comment from rhamilto on 2021-06-10 19:27:42 UTC ---

Will investigate next sprint.

@spadgett, did you see @jhadvig's question in https://bugzilla.redhat.com/show_bug.cgi?id=1967658#c1?

--- Additional comment from spadgett on 2021-06-10 20:13:05 UTC ---

To me, this seems like a bug. The message we're showing is not meaningful, and it should be a small change to fix.

Comment 1 Robb Hamilton 2021-07-02 12:17:12 UTC

PR open and awaiting group-lead-approved label.

Comment 2 Robb Hamilton 2021-07-21 11:57:23 UTC

PR open and awaiting group-lead-approved label.

Comment 6 errata-xmlrpc 2021-08-10 11:27:36 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.4 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:2983