Skip to content

Give more precise reasons for Subscriptions with no candidates. #2086

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

benluddy
Copy link
Contributor

@benluddy benluddy commented Apr 8, 2021

A Subscription specifies certain criteria for selecting operators from
catalogs. The granularity of the Subscription criteria is, from least
to most specific: catalog, package, channel, startingCSV (if
applicable). If a user creates a Subscription and its criteria does
not match a single operator, the failure message now indicates the
highest level of granularity that excludes all available
operators. For example, if a Subscription specifies a package name
that doesn't exist in the referenced, catalog, the specified package
name will appear in the failure text.

A Subscription specifies certain criteria for selecting operators from
catalogs. The granularity of the Subscription criteria is, from least
to most specific: catalog, package, channel, startingCSV (if
applicable). If a user creates a Subscription and its criteria does
not match a single operator, the failure message now indicates the
highest level of granularity that excludes all available
operators. For example, if a Subscription specifies a package name
that doesn't exist in the referenced, catalog, the specified package
name will appear in the failure text.

Signed-off-by: Ben Luddy <[email protected]>
@openshift-ci-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: benluddy

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 8, 2021
@openshift-ci
Copy link

openshift-ci bot commented Apr 8, 2021

@benluddy: The following test failed, say /retest to rerun all failed tests:

Test name Commit Details Rerun command
ci/prow/e2e-upgrade a486e54 link /test e2e-upgrade

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ecordell
Copy link
Member

ecordell commented Apr 8, 2021

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Apr 8, 2021
@openshift-merge-robot openshift-merge-robot merged commit 0bc157a into operator-framework:master Apr 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants