Bug 1882791 - Resolution failure messages should be discoverable from Subscription and/or related resources
Summary: Resolution failure messages should be discoverable from Subscription and/or r...
Status: CLOSED DUPLICATE of bug 1862846
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: OLM
Version: 4.6
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.7.0
Assignee: Evan Cordell
QA Contact: Jian Zhang
Depends On:
TreeView+ depends on / blocked
Reported: 2020-09-25 17:15 UTC by Ben Luddy
Modified: 2020-10-03 01:58 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2020-10-03 01:58:36 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1873030 0 high CLOSED Subscriptions without any candidate operators should cause resolution to fail 2021-02-24 15:17:05 UTC

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 ***

Note You need to log in before you can comment on or make changes to this bug.