-
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
The TaskRun did not fail promptly after the Pod experienced OOM #8170
Labels
kind/bug
Categorizes issue or PR as related to a bug.
Comments
l-qing
added a commit
to l-qing/pipeline
that referenced
this issue
Aug 2, 2024
fix tektoncd#8170 When an OOM occurs in a Pod related to TaskRun, the TaskRun should be marked as failed immediately instead of waiting for it to timeout.
l-qing
added a commit
to l-qing/pipeline
that referenced
this issue
Aug 2, 2024
…od OOM fix tektoncd#8170 When an OOM occurs in a Pod related to TaskRun, the TaskRun should be marked as failed immediately instead of waiting for it to timeout.
8 tasks
l-qing
added a commit
to l-qing/pipeline
that referenced
this issue
Aug 14, 2024
…od OOM fix tektoncd#8170 When an OOM occurs in a Pod related to TaskRun, the TaskRun should be marked as failed immediately instead of waiting for it to timeout.
l-qing
added a commit
to l-qing/pipeline
that referenced
this issue
Aug 23, 2024
…od OOM fix tektoncd#8170 When an OOM occurs in a Pod related to TaskRun, the TaskRun should be marked as failed immediately instead of waiting for it to timeout.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected Behavior
After the Pod experiences an OOM, the TaskRun can fail promptly.
Actual Behavior
The TaskRun is in Running state for a long time.
Steps to Reproduce the Problem
Additional Info
Kubernetes version:
Output of
kubectl version
:Tekton Pipeline version:
Output of
tkn version
orkubectl get pods -n tekton-pipelines -l app=tekton-pipelines-controller -o=jsonpath='{.items[0].metadata.labels.version}'
This issue has been present in several recent LTS versions, including v0.53, v0.56, v0.59, and v0.62
The text was updated successfully, but these errors were encountered: