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] node-kubelet-1.19 (ci-kubernetes-node-kubelet-1-19) #19155

Closed
hasheddan opened this issue Sep 9, 2020 · 4 comments
Closed

[Flaky Test] node-kubelet-1.19 (ci-kubernetes-node-kubelet-1-19) #19155

hasheddan opened this issue Sep 9, 2020 · 4 comments
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.

Comments

@hasheddan
Copy link
Contributor

What happened:

node-kubelet-1.19 (ci-kubernetes-node-kubelet-1-19) is flaking due to:

unable to create gce instance with running docker daemon for image cos-77-12371-1079-0.  could not create instance tmp-node-e2e-b43bd88b-cos-77-12371-1079-0: [&{Code:ZONE_RESOURCE_POOL_EXHAUSTED_WITH_DETAILS Location: Message:The zone 'projects/k8s-infra-e2e-boskos-070/zones/us-west1-b' does not have enough resources available to fulfill the request.  '(resource type:compute)'. ForceSendFields:[] NullFields:[]}]

What you expected to happen:

The job to run successfully.

Please provide links to example occurrences, if any:

https://prow.k8s.io/view/gcs/kubernetes-jenkins/logs/ci-kubernetes-node-kubelet-1-19/1303662016363237378
https://testgrid.k8s.io/sig-release-1.19-blocking#node-kubelet-1.19

Anything else we need to know?:

First occurrence: 21:44 PDT 09-08-20

@hasheddan hasheddan added the kind/bug Categorizes issue or PR as related to a bug. label Sep 9, 2020
@neolit123
Copy link
Member

The zone 'projects/k8s-infra-e2e-boskos-070/zones/us-west1-b' does not have enough resources available

could be a temporary outage since yesterday. we should probably wait for more runs.

/sig testing
/remove-kind bug
/kind flake

@k8s-ci-robot k8s-ci-robot added sig/testing Categorizes an issue or PR as relevant to SIG Testing. kind/flake Categorizes issue or PR as related to a flaky test. and removed kind/bug Categorizes issue or PR as related to a bug. labels Sep 9, 2020
@spiffxp
Copy link
Member

spiffxp commented Sep 11, 2020

/remove-sig testing
/sig node
Also I think these kinds of issues should be filed in kubenetes/kubernetes and not here

@k8s-ci-robot k8s-ci-robot added sig/node Categorizes an issue or PR as relevant to SIG Node. and removed sig/testing Categorizes an issue or PR as relevant to SIG Testing. labels Sep 11, 2020
@spiffxp
Copy link
Member

spiffxp commented Sep 11, 2020

@k8s-ci-robot
Copy link
Contributor

@spiffxp: Closing this issue.

In response to this:

/close
based on https://testgrid.k8s.io/sig-release-1.19-blocking#node-kubelet-1.19
Screen Shot 2020-09-10 at 7 26 09 PM

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.
Projects
None yet
Development

No branches or pull requests

4 participants