Bug 1882791

Summary: Resolution failure messages should be discoverable from Subscription and/or related resources
Product: OpenShift Container Platform Reporter: Ben Luddy <bluddy>
Component: OLMAssignee: Evan Cordell <ecordell>
OLM sub component: OLM QA Contact: Jian Zhang <jiazha>
Status: CLOSED DUPLICATE Docs Contact:
Severity: medium    
Priority: medium Keywords: UpcomingSprint
Version: 4.6   
Target Milestone: ---   
Target Release: 4.7.0   
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: 2020-10-03 01:58:36 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 Ben Luddy 2020-09-25 17:15:34 UTC 
When operator dependency resolution fails, the reasons for the failure appear in an Event. The Event's involvedObject is a Namespace (rather than a Subscription, for example), because dependency resolution considers everything within a single namespace at the same time. Also, since Events must reside in the same namespace as their involvedObject, and Namespace objects are cluster-scoped, these Events end up being created in the "default" namespace.

Users expect to be able to discover failure details from their existing resources. These details, or a reference to them, should be projected onto the status of all Subscriptions in the failing namespace.
Comment 1 Ben Luddy 2020-10-03 01:58:36 UTC 
Closing as a duplicate of the existing issue https://bugzilla.redhat.com/show_bug.cgi?id=1862846. Both relate to making dependency resolution errors apparent on Subscriptions et al.

*** This bug has been marked as a duplicate of bug 1862846 ***