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 apiserver [Disruptive] {Kubernetes e2e suite} #37508

Closed
k8s-github-robot opened this issue Nov 26, 2016 · 6 comments
Closed

[k8s.io] Services should work after restarting apiserver [Disruptive] {Kubernetes e2e suite} #37508

k8s-github-robot opened this issue Nov 26, 2016 · 6 comments
Assignees
@bowei @bprashanth
Labels
kind/flake Categorizes issue or PR as related to a flaky test. priority/backlog Higher priority than priority/awaiting-more-evidence. sig/network Categorizes an issue or PR as relevant to SIG Network.
Milestone
v1.6

Comments

@k8s-github-robot
Copy link

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

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

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/service.go:458
Expected error:
    <*net.OpError | 0xc421fb9270>: {
        Op: "dial",
        Net: "tcp",
        Source: nil,
        Addr: {
            IP: [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 255, 255, 130, 211, 210, 19],
            Port: 443,
            Zone: "",
        },
        Err: {
            Syscall: "getsockopt",
            Err: 0x6f,
        },
    }
    dial tcp 130.211.210.19:443: getsockopt: connection refused
not to have occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/service.go:448

Previous issues for this test: #28257 #29159 #29449 #32447
@k8s-github-robot k8s-github-robot added kind/flake Categorizes issue or PR as related to a flaky test. priority/backlog Higher priority than priority/awaiting-more-evidence. labels Nov 26, 2016
This was referenced Nov 26, 2016
Closed
Closed
Closed
Closed
Closed
Closed
Closed
Closed
Closed
Closed
Closed
Closed
Closed
Closed
Closed
Closed
Closed
Closed
Closed
Closed
Closed
Closed
Closed
Closed
Closed
Closed
Closed
This was referenced Jan 22, 2017
Closed
Closed
This was referenced Jan 31, 2017
Closed
Closed
Closed
Closed
@calebamiles calebamiles added the sig/network Categorizes an issue or PR as relevant to SIG Network. label Feb 27, 2017
@calebamiles calebamiles modified the milestone: v1.6 Mar 3, 2017
@bowei
Copy link
Member

bowei commented Mar 13, 2017

/assign @bowei

@bowei
Copy link
Member

bowei commented Mar 13, 2017

/close

not flake since Dec, 2016

@bowei
Copy link
Member

bowei commented Mar 13, 2017

/close

This was referenced Mar 17, 2017
Closed
Closed
Closed
Closed
Closed
This was referenced Mar 26, 2017
Closed
Closed
Closed
Closed
@k8s-github-robot k8s-github-robot mentioned this issue Apr 9, 2017
Closed
This was referenced Apr 24, 2017
Closed
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bowei bowei

@bprashanth bprashanth

Labels
kind/flake Categorizes issue or PR as related to a flaky test. priority/backlog Higher priority than priority/awaiting-more-evidence. sig/network Categorizes an issue or PR as relevant to SIG Network.
Projects
None yet
Milestone
v1.6
Development

No branches or pull requests
5 participants
@bowei @calebamiles @bprashanth @k8s-github-robot @k8s-ci-robot