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

[k8s.io] Services should be able to create a functioning NodePort service {Kubernetes e2e suite} #28569

Closed
k8s-github-robot opened this issue Jul 7, 2016 · 32 comments
Assignees
Labels
kind/flake Categorizes issue or PR as related to a flaky test. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/network Categorizes an issue or PR as relevant to SIG Network.
Milestone

Comments

@k8s-github-robot
Copy link

https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gke/10679/

Failed: [k8s.io] Services should be able to create a functioning NodePort service {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/service.go:403
Jul  6 19:51:55.035: expected node port 31810 to be in use, stdout: . err: Error running &{/workspace/kubernetes/platforms/linux/amd64/kubectl [kubectl --server=https://104.155.147.88 --kubeconfig=/workspace/.kube/config exec --namespace=e2e-tests-services-57c5g hostexec -- /bin/sh -c for i in $(seq 1 300); do if ss -ant46 'sport = :31810' | grep ^LISTEN; then exit 0; fi; sleep 1; done; exit 1] []  <nil>  error: google: could not find default credentials. See https://developers.google.com/accounts/docs/application-default-credentials for more information.
 [] <nil> 0xc8209224e0 exit status 1 <nil> true [0xc8201642d8 0xc820164398 0xc820164470] [0xc8201642d8 0xc820164398 0xc820164470] [0xc820164368 0xc820164448] [0xa9c260 0xa9c260] 0xc8215b3680}:
Command stdout:

stderr:
error: google: could not find default credentials. See https://developers.google.com/accounts/docs/application-default-credentials for more information.

error:
exit status 1

Previous issues for this test: #28064

@k8s-github-robot
Copy link
Author

k8s-github-robot commented Aug 29, 2016

Builds:
kubernetes-e2e-gci-gke-prod-parallel 224
kubernetes-e2e-gci-gke-staging-parallel 1347
kubernetes-e2e-gke-staging-parallel 7828

Failed: [k8s.io] Services should be able to create a functioning NodePort service {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/service.go:403
Aug 29 05:07:34.182: Failed waiting for pods to be running: Timeout waiting for 1 pods to be ready

@k8s-github-robot
Copy link
Author

[FLAKE-PING] @bprashanth

This flaky-test issue would love to have more attention...

@k8s-github-robot
Copy link
Author

[FLAKE-PING] @bprashanth

This flaky-test issue would love to have more attention.

@k8s-github-robot
Copy link
Author

[FLAKE-PING] @bprashanth

This flaky-test issue would love to have more attention.

1 similar comment
@k8s-github-robot
Copy link
Author

[FLAKE-PING] @bprashanth

This flaky-test issue would love to have more attention.

@k8s-github-robot
Copy link
Author

https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gci-gke-staging-parallel/529/

Failed: [k8s.io] Services should be able to create a functioning NodePort service {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/service.go:406
Oct  4 10:16:27.800: Failed waiting for pods to be running: Timeout waiting for 1 pods to be ready

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/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/network Categorizes an issue or PR as relevant to SIG Network.
Projects
None yet
Development

No branches or pull requests

6 participants