Skip to content
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

[sig-node] [ci-kubernetes-kind-e2e-parallel] Probing container should be restarted startup probe fails #100786

Closed
PriyankaH21 opened this issue Apr 2, 2021 · 7 comments
Assignees
Labels
kind/flake Categorizes issue or PR as related to a flaky test. sig/node Categorizes an issue or PR as relevant to SIG Node. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@PriyankaH21
Copy link

Which jobs are flaking: ci-kubernetes-kind-e2e-parallel

Which test(s) are flaking: Probing container should be restarted startup probe fails

Testgrid link:

`https://testgrid.k8s.io/sig-release-master-blocking#kind-master-parallel&include-filter-by-regex=Probing%20container%20should%20be%20restarted%20startup%20probe%20fails

Reason for failure:

• Failure [302.520 seconds]
[sig-node] Probing container
/home/prow/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/common/node/framework.go:23
  should be restarted startup probe fails [It]
  /home/prow/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/common/node/container_probe.go:293
  Apr  2 15:50:01.966: starting pod startup-7fd090d4-8e3f-4c39-bdf6-73d465262262 in namespace container-probe-5226
      
  Unexpected error:
      <*errors.errorString | 0xc00024a250>: {
          s: "timed out waiting for the condition",
      }
      timed out waiting for the condition
  occurred
  /home/prow/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/common/node/container_probe.go:655
------------------------------
{"msg":"FAILED [sig-node] Probing container should be restarted startup probe fails","total":-1,"completed":5,"skipped":89,"failed":1,"failures":["[sig-node] Probing container should be restarted startup probe fails"]}

Anything else we need to know:

Triage Link: https://storage.googleapis.com/k8s-gubernator/triage/index.html

Notes: 1 clusters of 1 failures out of 125086 builds from 3/18/2021, 8:00:07 PM to 4/2/2021, 11:57:06 AM.

/sig node

@PriyankaH21 PriyankaH21 added the kind/flake Categorizes issue or PR as related to a flaky test. label Apr 2, 2021
@k8s-ci-robot k8s-ci-robot added sig/node Categorizes an issue or PR as relevant to SIG Node. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Apr 2, 2021
@SergeyKanzhelev
Copy link
Member

/triage accepted

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Apr 21, 2021
@SergeyKanzhelev
Copy link
Member

/assign @matthyx

can you take a look?

/cc @jackfrancis @wzshiming

@jackfrancis
Copy link
Contributor

I see only one flake in the last ~25 days:

https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-kubernetes-kind-e2e-parallel/1383544572180697088

(that test run has a bunch of other failures too)

Definitely wanna make sure these tests are rock solid, lemme know if I can help.

@matthyx
Copy link
Contributor

matthyx commented Apr 22, 2021

Agreed with @jackfrancis this is not flacky...
Unlike #99998 which is really having a hard time.

@wzshiming
Copy link
Member

Agreed with @jackfrancis @matthyx.

@SergeyKanzhelev
Copy link
Member

/close

@k8s-ci-robot
Copy link
Contributor

@SergeyKanzhelev: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/flake Categorizes issue or PR as related to a flaky test. sig/node Categorizes an issue or PR as relevant to SIG Node. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
Archived in project
Development

No branches or pull requests

6 participants