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

e2e flake: Services should work after restarting kube-proxy #18283

Closed
gmarek opened this issue Dec 7, 2015 · 2 comments
Closed

e2e flake: Services should work after restarting kube-proxy #18283

gmarek opened this issue Dec 7, 2015 · 2 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.

Comments

@gmarek
Copy link
Contributor

gmarek commented Dec 7, 2015

Services should work after restarting kube-proxy

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/service.go:310 Expected error: <*errors.errorString | 0xc208be1ca0>: { s: "service verification failed for:\n set -e; for i in $(seq 1 9); do wget -q -T 1 -O - http://10.0.197.126:80 || true; echo; done | sort -n | uniq", } service verification failed for: set -e; for i in $(seq 1 9); do wget -q -T 1 -O - http://10.0.197.126:80 || true; echo; done | sort -n | uniq not to have occurred

http://kubekins.dls.corp.google.com/view/Critical%20Builds/job/kubernetes-e2e-gce/9774/

cc @kubernetes/goog-cluster

@gmarek gmarek added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. team/cluster kind/flake Categorizes issue or PR as related to a flaky test. labels Dec 7, 2015
@piosz
Copy link
Member

piosz commented Dec 7, 2015

assigning @thockin for triage

@thockin
Copy link
Member

thockin commented Dec 14, 2015

Found a bug which could be contributing to this. PR forthcoming

thockin added a commit to thockin/kubernetes that referenced this issue Dec 14, 2015
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.
Projects
None yet
Development

No branches or pull requests

3 participants