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

[Flaky test] Conformance - GCE - master - kubetest2 #118928

Closed
mehabhalodiya opened this issue Jun 28, 2023 · 6 comments · Fixed by #118935
Closed

[Flaky test] Conformance - GCE - master - kubetest2 #118928

mehabhalodiya opened this issue Jun 28, 2023 · 6 comments · Fixed by #118935
Assignees
Labels
kind/flake Categorizes issue or PR as related to a flaky test. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. sig/apps Categorizes an issue or PR as relevant to SIG Apps. sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@mehabhalodiya
Copy link

Which jobs are failing?

master-blocking

  • Conformance - GCE - master - kubetest2

Which tests are failing?

  • Kubernetes e2e suite.[It] [sig-apps] Daemon set [Serial] should rollback without unnecessary restarts [Conformance] Changes
  • ci-kubernetes-gce-conformance-latest-kubetest2.Overall Changes
  • kubetest2.Test Changes

Screenshot from 2023-06-28 15-01-46

Since when has it been failing?

2023-06-27 16:43 PDT

Testgrid link

https://testgrid.k8s.io/sig-release-master-blocking#Conformance%20-%20GCE%20-%20master%20-%20kubetest2

Reason for failure (if possible)

Kubernetes e2e suite: [It] [sig-apps] Daemon set [Serial] should rollback without unnecessary restarts [Conformance] 

{ failed [FAILED] unexpected pod daemon-set-lmdd2 be restarted In [It] at: test/e2e/apps/daemon_set.go:500 @ 06/28/23 07:35:29.181 }

Anything else we need to know?

No response

Relevant SIG(s)

/sig cloud-provider
/sig apps
cc @kubernetes/ci-signal

@mehabhalodiya mehabhalodiya added the kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. label Jun 28, 2023
@k8s-ci-robot k8s-ci-robot added sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider. sig/apps Categorizes an issue or PR as relevant to SIG Apps. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Jun 28, 2023
@aojea
Copy link
Member

aojea commented Jun 28, 2023

@k8s-ci-robot k8s-ci-robot added the priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. label Jun 28, 2023
@alculquicondor
Copy link
Member

/assign

@mehabhalodiya
Copy link
Author

@aojea @alculquicondor @soltysh anyone from you can please add /triage accepted to this issue?

@alculquicondor
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 Jun 28, 2023
@alculquicondor
Copy link
Member

I have a proposed fix in #118935.
Is there a job I can add?

@mehabhalodiya mehabhalodiya changed the title [Failing test] Conformance - GCE - master - kubetest2 [Flaky test] Conformance - GCE - master - kubetest2 Jun 28, 2023
@Vyom-Yadav
Copy link
Member

/remove-kind failing-test
/kind flake

@k8s-ci-robot k8s-ci-robot added kind/flake Categorizes issue or PR as related to a flaky test. and removed kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. labels Jun 29, 2023
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. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. sig/apps Categorizes an issue or PR as relevant to SIG Apps. sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
Development

Successfully merging a pull request may close this issue.

5 participants