Skip to content

[Flake] PreStop graceful pod terminated should wait until preStop hook completes the process #106125

Closed
@liggitt

Description

Which jobs are flaking?

ci-kubernetes-e2e-gci-gce
pull-kubernetes-e2e-gce-ubuntu-containerd

Which tests are flaking?

[sig-node] PreStop graceful pod terminated should wait until preStop hook completes the process

This is the flakiest test both in the CI (ci-kubernetes-e2e-gci-gce) and PR (pr:pull-kubernetes-e2e-gce-ubuntu-containerd) e2e according to http://storage.googleapis.com/k8s-metrics/flakes-latest.json:

  "pr:pull-kubernetes-e2e-gce-ubuntu-containerd": {
    "consistency": 0.937,
    "flakes": 29,
    "test_flakes": {
      "[sig-node] PreStop graceful pod terminated should wait until preStop hook completes the process": 10,
      "[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should honor timeout [Conformance]": 4,
      "[sig-storage] Downward API volume should update annotations on modification [NodeConformance] [Conformance]": 3,
...
  "ci-kubernetes-e2e-gci-gce": {
    "consistency": 0.661,
    "flakes": 20,
    "test_flakes": {
      "[sig-node] PreStop graceful pod terminated should wait until preStop hook completes the process": 17,
      "[sig-network] Proxy version v1 should proxy logs on node using proxy subresource ": 5,
      "[sig-api-machinery] AdmissionWebhook [Privileged:ClusterAdmin] should honor timeout [Conformance]": 3,
...

Since when has it been flaking?

Several weeks

Testgrid link

No response

Reason for failure (if possible)

https://storage.googleapis.com/k8s-triage/index.html?ci=0&pr=1&test=PreStop%20graceful%20pod%20terminated%20should%20wait%20until%20preStop%20hook%20completes%20the%20process

Anything else we need to know?

No response

Relevant SIG(s)

/sig node
/priority important-soon

Metadata

Assignees

Labels

kind/flakeCategorizes issue or PR as related to a flaky test.lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.priority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.sig/nodeCategorizes an issue or PR as relevant to SIG Node.triage/acceptedIndicates an issue or PR is ready to be actively worked on.

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions