-
Notifications
You must be signed in to change notification settings - Fork 71
Bug 2039135: add more descriptive error message to pruning of FBC #308
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
Bug 2039135: add more descriptive error message to pruning of FBC #308
Conversation
Hi @jbuchananr. Thanks for your PR. I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
…sed in pruning * add: create regression test for fbc error message Signed-off-by: Jonathan Buchanan <[email protected]> Upstream-repository: operator-registry Upstream-commit: 64c2f24da4f01f4a6eb1f3a87aa0bf7676e241e9
3f9e94f
to
5bbcf10
Compare
/ok-to-test |
/bugzilla refresh |
@tylerslaton: No Bugzilla bug is referenced in the title of this pull request. In response to this:
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. |
@jbuchananr: This pull request references Bugzilla bug 2039135, which is invalid:
Comment In response to this:
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. |
/bugzilla refresh |
@jbuchananr: This pull request references Bugzilla bug 2039135, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
No GitHub users were found matching the public email listed for the QA contact in Bugzilla ([email protected]), skipping review request. In response to this:
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. |
/retest |
@jbuchananr: all tests passed! 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. |
/label qe-approved |
/lgtm |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jbuchananr, perdasilva 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 |
@jbuchananr: All pull requests linked via external trackers have merged: Bugzilla bug 2039135 has been moved to the MODIFIED state. In response to this:
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. |
At the time of making this commit, the package `github.com/ghodss/yaml` is no longer actively maintained. `sigs.k8s.io/yaml` is a permanent fork of `ghodss/yaml` and is actively maintained by Kubernetes SIG. Signed-off-by: Eng Zer Jun <[email protected]> Upstream-repository: api Upstream-commit: 5efe1a23d8c21e51c6a63a472a0d5320342187ec
Description of the change:
Provides a more descriptive error when opm index prune is called on a file based catalog letting users know that it only supports sqlite-based catalogs.
Motivation for the change:
Currently, an unclear error message is thrown while calling opm index prune on a file based catalog.
E.g "Error: index image xxxx missing label operators.operatorframework.io.index.database.v1"
Note:
Do we want to backport this to 4.10?
Signed-off-by: Jonathan Buchanan [email protected]
Upstream-repository: operator-registry
Upstream-commit: 64c2f24da4f01f4a6eb1f3a87aa0bf7676e241e9