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

[windows] Failure cluster [4482c2b4...] [sig-node] Pods should contain environment variables for services #110339

Closed
dims opened this issue Jun 1, 2022 · 4 comments
Labels
kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. sig/windows Categorizes an issue or PR as relevant to SIG Windows. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects

Comments

@dims
Copy link
Member

dims commented Jun 1, 2022

Failure cluster 4482c2b4cf127b8c4ebe

Error text:
test/e2e/framework/framework.go:647
May 27 19:00:53.684: Unexpected error:
    <*pod.timeoutError | 0xc0033572e0>: {
        msg: "timed out while waiting for pod pods-6773/server-envvars-673b9176-ce7e-4df0-88f7-454920c03d5f to be running and ready",
    }
    timed out while waiting for pod pods-6773/server-envvars-673b9176-ce7e-4df0-88f7-454920c03d5f to be running and ready
occurred
test/e2e/framework/pods.go:107

Recent failures:

6/1/2022, 1:52:06 PM ci-kubernetes-e2e-capz-master-containerd-windows-2022
6/1/2022, 12:33:07 PM ci-kubernetes-e2e-capz-master-containerd-windows
6/1/2022, 10:51:06 AM ci-kubernetes-e2e-capz-master-containerd-windows-2022
6/1/2022, 10:15:59 AM ci-kubernetes-e2e-windows-containerd-gce-master
6/1/2022, 10:15:59 AM ci-kubernetes-e2e-windows-20h2-containerd-gce-master

/kind failing-test

/sig windows

@k8s-ci-robot k8s-ci-robot added kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. sig/windows Categorizes an issue or PR as relevant to SIG Windows. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Jun 1, 2022
@jsturtevant
Copy link
Contributor

should be fixed by #110235

@jsturtevant
Copy link
Contributor

/triage accepted
/priority critical-urgent

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Jun 1, 2022
@marosset marosset added this to Flaky Tests in SIG-Windows Jun 2, 2022
@jsturtevant
Copy link
Contributor

fixed by #110235
/close

@k8s-ci-robot
Copy link
Contributor

@jsturtevant: Closing this issue.

In response to this:

fixed by #110235
/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.

SIG-Windows automation moved this from Flaky Tests to Done (v1.25) Jun 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. sig/windows Categorizes an issue or PR as relevant to SIG Windows. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
SIG-Windows
  
Done (v1.25)
Development

No branches or pull requests

3 participants