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.

Sign up for GitHub

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

Jump to bottom

[k8s.io] Services should work after restarting kube-proxy [Disruptive] {Kubernetes e2e suite} #29514

Closed
k8s-github-robot opened this issue Jul 23, 2016 · 24 comments
Closed

[k8s.io] Services should work after restarting kube-proxy [Disruptive] {Kubernetes e2e suite} #29514

k8s-github-robot opened this issue Jul 23, 2016 · 24 comments
Assignees
@bprashanth
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.
Milestone
v1.5

Comments

@k8s-github-robot
Copy link

https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gce-serial/1778/

Failed: [k8s.io] Services should work after restarting kube-proxy [Disruptive] {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/service.go:328
Expected error:
    <*errors.errorString | 0xc8208a00e0>: {
        s: "service verification failed for: 10.0.175.223\nexpected [service1-3zrya service1-b2dbs service1-dcon7]\nreceived [wget: can't connect to remote host (10.0.175.223): No route to host wget: download timed out]",
    }
    service verification failed for: 10.0.175.223
    expected [service1-3zrya service1-b2dbs service1-dcon7]
    received [wget: can't connect to remote host (10.0.175.223): No route to host wget: download timed out]
not to have occurred
@k8s-github-robot k8s-github-robot added priority/backlog Higher priority than priority/awaiting-more-evidence. kind/flake Categorizes issue or PR as related to a flaky test. labels Jul 23, 2016
@k8s-github-robot k8s-github-robot mentioned this issue Jul 25, 2016
Closed
@k8s-github-robot
Copy link
Author

https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gce-serial/1791/

Failed: [k8s.io] Services should work after restarting kube-proxy [Disruptive] {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/service.go:328
Expected error:
    <*errors.errorString | 0xc821336070>: {
        s: "service verification failed for: 10.0.242.19\nexpected [service1-lro2s service1-qu2a4 service1-tfkpu]\nreceived [service1-qu2a4 service1-tfkpu]",
    }
    service verification failed for: 10.0.242.19
    expected [service1-lro2s service1-qu2a4 service1-tfkpu]
    received [service1-qu2a4 service1-tfkpu]
not to have occurred

@k8s-github-robot
Copy link
Author

https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gce-serial/1795/

Failed: [k8s.io] Services should work after restarting kube-proxy [Disruptive] {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/service.go:328
Expected error:
    <*errors.errorString | 0xc82097ac00>: {
        s: "service verification failed for: 10.0.166.127\nexpected [service2-1wilr service2-i603v service2-uj1q3]\nreceived [service2-i603v service2-uj1q3]",
    }
    service verification failed for: 10.0.166.127
    expected [service2-1wilr service2-i603v service2-uj1q3]
    received [service2-i603v service2-uj1q3]
not to have occurred

@k8s-github-robot k8s-github-robot added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. and removed priority/backlog Higher priority than priority/awaiting-more-evidence. labels Jul 26, 2016
@k8s-github-robot
Copy link
Author

https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gce-serial/1890/

Failed: [k8s.io] Services should work after restarting kube-proxy [Disruptive] {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/service.go:331
Expected error:
    <*errors.errorString | 0xc820f888b0>: {
        s: "service verification failed for: 10.0.161.193\nexpected [service2-65a4t service2-l7c6e service2-rdwuu]\nreceived [service2-65a4t service2-l7c6e]",
    }
    service verification failed for: 10.0.161.193
    expected [service2-65a4t service2-l7c6e service2-rdwuu]
    received [service2-65a4t service2-l7c6e]
not to have occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/service.go:311

@k8s-github-robot
Copy link
Author

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

Failed: [k8s.io] Services should work after restarting kube-proxy [Disruptive] {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/service.go:331
Expected error:
    <*errors.errorString | 0xc82135e080>: {
        s: "service verification failed for: 10.183.249.235\nexpected [service1-4juhn service1-ckfhm service1-qyszt]\nreceived [wget: can't connect to remote host (10.183.249.235): No route to host wget: download timed out]",
    }
    service verification failed for: 10.183.249.235
    expected [service1-4juhn service1-ckfhm service1-qyszt]
    received [wget: can't connect to remote host (10.183.249.235): No route to host wget: download timed out]
not to have occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/service.go:329

@k8s-github-robot k8s-github-robot mentioned this issue Aug 17, 2016
Closed
@k8s-github-robot
Copy link
Author

https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gce-serial/1980/

Failed: [k8s.io] Services should work after restarting kube-proxy [Disruptive] {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/service.go:331
Expected error:
    <*errors.errorString | 0xc820bb3c30>: {
        s: "service verification failed for: 10.0.3.209\nexpected [service1-1cl2a service1-837ez service1-vhmfo]\nreceived [service1-837ez service1-vhmfo]",
    }
    service verification failed for: 10.0.3.209
    expected [service1-1cl2a service1-837ez service1-vhmfo]
    received [service1-837ez service1-vhmfo]
not to have occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/service.go:310

@k8s-github-robot
Copy link
Author

https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gce-serial/1989/

Failed: [k8s.io] Services should work after restarting kube-proxy [Disruptive] {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/service.go:331
Expected error:
    <*errors.errorString | 0xc8211cc110>: {
        s: "service verification failed for: 10.0.203.73\nexpected [service1-5yprn service1-7kuro service1-n7o85]\nreceived [wget: can't connect to remote host (10.0.203.73): No route to host wget: download timed out]",
    }
    service verification failed for: 10.0.203.73
    expected [service1-5yprn service1-7kuro service1-n7o85]
    received [wget: can't connect to remote host (10.0.203.73): No route to host wget: download timed out]
not to have occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/service.go:329

@mikedanese
Copy link
Member

mikedanese commented Aug 25, 2016 •
edited

ref #31448

@bprashanth
Copy link
Contributor

going to take a look at disruptie e2e failures (#29514, #29449) right after I'm done with validating #31559

@bprashanth bprashanth mentioned this issue Aug 29, 2016
Closed
@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-gke-serial/2210/

Failed: [k8s.io] Services should work after restarting kube-proxy [Disruptive] {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/service.go:385
Expected error:
    <*errors.errorString | 0xc820734090>: {
        s: "service verification failed for: 10.183.254.164\nexpected [service1-glwo3 service1-plxvf service1-rjwn0]\nreceived [wget: can't connect to remote host (10.183.254.164): No route to host wget: download timed out]",
    }
    service verification failed for: 10.183.254.164
    expected [service1-glwo3 service1-plxvf service1-rjwn0]
    received [wget: can't connect to remote host (10.183.254.164): No route to host wget: download timed out]
not to have occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/service.go:364

@k8s-github-robot
Copy link
Author

[FLAKE-PING] @bprashanth

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

2 similar comments
@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.

@davidopp
Copy link
Member

davidopp commented Sep 18, 2016 •
edited

failed in
https://k8s-testgrid.appspot.com/google-1.2-1.4-upgrade#gke-cvm-1.2-cvm-1.4-upgrade-master
https://k8s-testgrid.appspot.com/google-1.3-1.4-upgrade#gke-gci-1.3-gci-1.4-upgrade-master

@pwittrock pwittrock added the priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. label Sep 18, 2016
@pwittrock pwittrock added this to the v1.4 milestone Sep 18, 2016
@pwittrock pwittrock removed the priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. label Sep 18, 2016
@bprashanth
Copy link
Contributor

The CVM failures in 1.2->1.4 (https://k8s-testgrid.appspot.com/google-1.2-1.4-upgrade#gke-cvm-1.2-cvm-1.4-upgrade-master) are #32124 (comment) and should be addressed with #33204

@k8s-github-robot k8s-github-robot mentioned this issue Sep 23, 2016
Closed
This was referenced Dec 30, 2016
Closed
Closed
Closed
Closed
This was referenced Jan 10, 2017
Closed
Closed
Closed
This was referenced Jan 21, 2017
Closed
Closed
Closed
Closed
Closed
Closed
This was referenced Jan 30, 2017
Closed
Closed
Closed
Closed
@k8s-github-robot k8s-github-robot mentioned this issue Feb 28, 2017
Closed
This was referenced Mar 14, 2017
Closed
Closed
This was referenced Mar 21, 2017
Closed
Closed
Closed
This was referenced Mar 29, 2017
Closed
Closed
This was referenced Apr 8, 2017
Closed
Closed
This was referenced Apr 27, 2017
Closed
Closed
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bprashanth bprashanth

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
Milestone
v1.5
Development

No branches or pull requests
6 participants
@calebamiles @mikedanese @pwittrock @davidopp @bprashanth @k8s-github-robot