kubernetes: [Failing Test] [k8s.io] Probing container should be restarted with a docker exec liveness probe with timeout [ci-kubernetes-e2e-ubuntu-gce]
Which jobs are failing:
gce-ubuntu-master-default (ci-kubernetes-e2e-ubuntu-gce)
Which test(s) are failing:
[k8s.io] Probing container should be restarted with a docker exec liveness probe with timeout
Since when has it been failing:
11-09-20 18:43 PST
Testgrid link:
https://testgrid.k8s.io/sig-release-master-informing#gce-ubuntu-master-default
Reason for failure:
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/container_probe.go:214
Nov 10 03:11:15.973: pod container-probe-9373/busybox-723ec292-164c-46d1-b47b-b0761bee2121 - expected number of restarts: 1, found restarts: 0
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/container_probe.go:223
Anything else we need to know:
Test flipped to failing and has consistently been failing since. Commit failure started on: https://github.com/kubernetes/kubernetes/commits/734889ed8 Looks like it is related to this PR: https://github.com/kubernetes/kubernetes/pull/94115
/sig node /priority critical-urgent /cc @kubernetes/ci-signal /assign @hasheddan /milestone v1.20
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 1
- Comments: 16 (16 by maintainers)
Commits related to this issue
- Explicitly enable probing container test for dockershim job Explicitly enables `[k8s.io] Probing container should be restarted startup probe fails` to test against a job using dockershim nodes to gua... — committed to hasheddan/test-infra by hasheddan 4 years ago
- Explicitly enable probing container test for dockershim job Explicitly enables `[k8s.io] Probing container should be restarted startup probe fails` to test against a job using dockershim nodes to gua... — committed to hasheddan/test-infra by hasheddan 4 years ago
The test should be passing on docker though, so it’s possibly a legitable failure