Skip to content

[Failing Test] [k8s.io] Probing container should be restarted with a docker exec liveness probe with timeout [ci-kubernetes-e2e-ubuntu-gce] #96463

@hasheddan

Description

@hasheddan

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: #94115

/sig node
/priority critical-urgent
/cc @kubernetes/ci-signal
/assign @hasheddan
/milestone v1.20

Metadata

Metadata

Assignees

Labels

kind/failing-testCategorizes issue or PR as related to a consistently or frequently failing test.needs-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.priority/critical-urgentHighest priority. Must be actively worked on as someone's top priority right now.sig/nodeCategorizes an issue or PR as relevant to SIG Node.

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions