-
Notifications
You must be signed in to change notification settings - Fork 551
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
Fixes difficult to understand error message when CSV is missing APIVersion #2673
Fixes difficult to understand error message when CSV is missing APIVersion #2673
Conversation
Hi @nsapse. Thanks for your PR. I'm waiting for a operator-framework 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. |
4c8975b
to
9041dc1
Compare
/ok-to-test |
Just a friendly reminder here is that you need to identify if an e2e test case is needed. The unit test is preferred if e2e is unnecessary. |
036040f
to
6777815
Compare
f29005f
to
a64cf99
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice job -- I just had a thought on the overall purpose of the implementation. Code-wise everything looks good.
d791f41
to
5d9fc52
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
small nit: the commit message should be updated to reflect the new fatal error type.
After that, this LGTM
Realizing that the test currently references a quay repo in my own repo rather than the |
2fab6f4
to
fe54a3c
Compare
/lgtm |
- Modified bundle unpacking to fail installPlan with a nice message if after unbundling csv manifests APIVersion or Kind are blank. - Adds FatalError type to return to checked when syncing install plans to see if the error causing issues is fatal or should cause the IP to be transitioned to failed state. - Makes installPlan fail with a nicer more user friendly message than the current difficult to understand message regarding serviceAccounts. - Adds tests using internal magic-catalog library to confirm that unpacking fails when APIVersion is blank. Signed-off-by: Noah Sapse <[email protected]>
/lgtm |
noice! You're a legend, thank you @nsapse |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: exdx, nsapse, 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 |
Description of the change:
Modifies CSV unbundle process so that after unbundling APIVersion or Kind are missing the installPlan is failed and the user receives a helpful and descriptive failure message letting them know that data was missing.
Motivation for the change:
Per BZ#1982737 currently when a CSV is missing APIVersion the associated installPlan fails with a cryptic message involving failure to create a service account. I initially tried to solve this by inferring the APIVersion if left blank per PR#2609 however the conversation following the PR made it clear that approach was not an acceptable fix.
Reviewer Checklist
/doc
[FLAKE]
are truly flaky[FLAKE]
tag are no longer flaky