Bug 1921954

Summary: Subscription-related constraints in ResolutionFailed events are misleading
Product: OpenShift Container Platform Reporter: Ben Luddy <bluddy>
Component: OLMAssignee: Ben Luddy <bluddy>
OLM sub component: OLM QA Contact: Tom Buskey <tbuskey>
Status: CLOSED ERRATA Docs Contact:
Severity: medium    
Priority: medium CC: bluddy, krizza, pneedle
Version: 4.6Keywords: Triaged, UpcomingSprint
Target Milestone: ---   
Target Release: 4.7.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-02-24 15:57:12 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:

Description Ben Luddy 2021-01-28 23:29:25 UTC
Description of problem:

If no available operators are found that match the spec of a Subscription, the constraints listed in the ResolutionFailed event are misleading.

For example:

> constraints not satisfiable: ibm-appconnect is mandatory, ibm-appconnect has a dependency without any candidates to satisfy it

means

> The namespace contains a subscription for package "ibm-appconnect" and no operators were found in the catalog that match the criteria in the subscription's spec.


Version-Release number of selected component (if applicable): 4.6+


How reproducible: Always


Steps to Reproduce:
1. Create a subscription for a package that doesn't exist.
2. Look for the ResolutionFailed event in the default namespace:
$ kubectl get event --sort-by=.metadata.creationTimestamp | grep ResolutionFailed | tail -1

Actual results: see above.


Expected results, approximately:

X is mandatory -> a subscription to package X exists in the namespace
X has a dependency without any candidates to satisfy it -> no operators were found matching the criteria of the subscription

Comment 1 Kevin Rizza 2021-02-01 15:27:23 UTC
Marking for upcoming sprint and removing from 4.7.0 release list. This will be addressed in a future sprint.

Comment 9 errata-xmlrpc 2021-02-24 15:57:12 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.7.0 security, bug fix, and enhancement 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-2020:5633