-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
PipelineRun fails to timeout properly in v0.63.0 (hits PipelineRunCouldntTimeOut state) #8230
Labels
kind/bug
Categorizes issue or PR as related to a bug.
Milestone
Comments
Thank you for your feedback. I looked at it today. |
l-qing
added a commit
to l-qing/pipeline
that referenced
this issue
Sep 3, 2024
fix tektoncd#8230 When the PipelineRun timeout, validation errors returned when patch a completed TaskRun should be ignored.
l-qing
added a commit
to l-qing/pipeline
that referenced
this issue
Sep 3, 2024
…ssfully fix tektoncd#8230 When the PipelineRun timeout, validation errors returned when patch a completed TaskRun should be ignored.
8 tasks
l-qing
added a commit
to l-qing/pipeline
that referenced
this issue
Sep 5, 2024
…ssfully fix tektoncd#8230 When the PipelineRun timeout, validation errors returned when patch a completed TaskRun should be ignored.
l-qing
added a commit
to l-qing/pipeline
that referenced
this issue
Sep 6, 2024
…ssfully fix tektoncd#8230 When the PipelineRun timeout, validation errors returned when patch a completed TaskRun should be ignored.
l-qing
added a commit
to l-qing/pipeline
that referenced
this issue
Sep 13, 2024
…ssfully fix tektoncd#8230 When the PipelineRun timeout, validation errors returned when patch a completed TaskRun should be ignored.
l-qing
added a commit
to l-qing/pipeline
that referenced
this issue
Sep 17, 2024
…ssfully fix tektoncd#8230 When the PipelineRun timeout, validation errors returned when patch a completed TaskRun should be ignored.
l-qing
added a commit
to l-qing/pipeline
that referenced
this issue
Sep 19, 2024
…ssfully fix tektoncd#8230 When the PipelineRun timeout, validation errors returned when patch a completed TaskRun should be ignored.
tekton-robot
pushed a commit
to tekton-robot/pipeline
that referenced
this issue
Sep 24, 2024
…ssfully fix tektoncd#8230 When the PipelineRun timeout, validation errors returned when patch a completed TaskRun should be ignored.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected Behavior
Creating a pipelinerun with a timeout set that has multiple tasks, where some complete before the timeout expires should properly timeout.
Actual Behavior
The pipelinerun resource hits a "PipelineRunCouldntTimeout" state with the following error:
Steps to Reproduce the Problem
See the following gist for an easy way to reproduce: https://gist.github.com/hrivera-ntap/a9dc47e7924feb6dc3ad32ac13751ffb
Additional Info
Kubernetes version:
Output of
kubectl version
:v0.63.0
v0.62.x
(appears to be a regression introduced after v0.61.1)
@l-qing : This appears to be closely related to the issue reported in #8172 that you recently fixed by #8173. Mind taking a look?
The text was updated successfully, but these errors were encountered: