kubernetes: [Failing Job] pull-kubernetes-node-e2e-containerd is timing out
Which jobs are failing: pull-kubernetes-node-e2e-containerd
Which test(s) are failing: Timeout
Since when has it been failing:
- Last good run (2020-04-03 11:00:09 +0000 UTC): https://prow.k8s.io/view/gcs/kubernetes-jenkins/pr-logs/directory/pull-kubernetes-node-e2e-containerd/1246029654804926464
- First bad run (2020-04-03 12:37:42 +0000 UTC): https://prow.k8s.io/view/gcs/kubernetes-jenkins/pr-logs/directory/pull-kubernetes-node-e2e-containerd/1246054193446260736
- Latest bad run (2020-04-04 01:19:40 +0000 UTC): https://prow.k8s.io/view/gcs/kubernetes-jenkins/pr-logs/directory/pull-kubernetes-node-e2e-containerd/1246245958304403456
Testgrid link: https://testgrid.k8s.io/sig-node-containerd#pull-node-e2e
Reason for failure:
kubetest --timeout triggered
Anything else we need to know:
- triage link: https://storage.googleapis.com/k8s-gubernator/triage/index.html?pr=1&job=pull-kubernetes-node-e2e-containerd
This isn’t a merge-blocking test but it is reporting on all PRs
/sig node /sig release /priority important-soon
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 1
- Comments: 19 (19 by maintainers)
Getting this to run over in wg-k8s-infra is going to take some time. Expect something in the next two weeks. (ref: https://github.com/kubernetes/k8s.io/issues/752#issuecomment-621371086)
As these aren’t release blocking or merge blocking tests I haven’t spent time dissecting whether there is something unique about this project that requires it be used for containerd tests. Someone is welcome to try assigning one of these to the node-e2e-project pool and see what happens.