-
Notifications
You must be signed in to change notification settings - Fork 1.8k
fix: do not fail PipelineRun when TaskRef reconciles with retryable err #9099
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
fix: do not fail PipelineRun when TaskRef reconciles with retryable err #9099
Conversation
|
/kind fix |
|
@aThorp96: The label(s) 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. |
|
/kind bug |
03e4771 to
b77b00a
Compare
With this change, no `ErrCouldntValidateObjectRetryable` returned by DryRunValidate results in a PipelineRun being marked as failed. Previously, the only errors which were actually retried were naming conflicts, server-timeouts, timeouts, and too-many-requests. Unknown errors were marked as "Retryable", however they still caused the PipelineRun to fail since `resolutioncommon.IsErrTransient` did not check if the err was of type `ErrCouldntValidateObjectRetryable`
b77b00a to
c5d3a6d
Compare
|
/retest |
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.
/lgtm
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: vdemeester, waveywaves 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 |
Changes
With this change, no
ErrCouldntValidateObjectRetryablereturned by DryRunValidate results in a PipelineRun being marked as failed. Previously, the only errors which were actually retried were naming conflicts, server-timeouts, timeouts, and too-many-requests. Unknown errors were still marked as Retryable, but they still caused the pipelinerun to fail.Submitter Checklist
As the author of this PR, please check off the items in this checklist:
/kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tepRelease Notes