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] Networking [k8s.io] Granular Checks should function for pod communication between nodes {Kubernetes e2e suite} #31402

Closed
k8s-github-robot opened this issue Aug 25, 2016 · 61 comments
Assignees
Labels
kind/flake Categorizes issue or PR as related to a flaky test. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now.
Milestone

Comments

@k8s-github-robot
Copy link

https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/pr-logs/pull/31354/kubernetes-pull-build-test-e2e-gce/55878/

Failed: [k8s.io] Networking [k8s.io] Granular Checks should function for pod communication between nodes {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/networking.go:50
Aug 24 18:15:37.902: Unexpected error code, expected 200, got, 500 (&{500 Internal Server Error 500 HTTP/1.1 1 1 map[Content-Type:[text/html; charset=UTF-8] Date:[Thu, 25 Aug 2016 01:15:37 GMT] Server:[gws] Content-Length:[1730] X-Xss-Protection:[1; mode=block] X-Frame-Options:[SAMEORIGIN]] 0xc820963400 1730 [] false map[] 0xc82059c000 <nil>})
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/networking.go:48

Happened on a presubmit run in #31354.

Previous issues for this test: #30131

@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 Aug 25, 2016
@k8s-github-robot
Copy link
Author

[FLAKE-PING] @freehan

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-staging-parallel/8189/

Failed: [k8s.io] Networking [k8s.io] Granular Checks should function for pod communication between nodes {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/networking.go:267
Expected error:
    <*errors.errorString | 0xc820b08a10>: {
        s: "pod 'different-node-wget' terminated with failure: &{ExitCode:1 Signal:0 Reason:Error Message: StartedAt:{Time:2016-09-05 17:38:13 -0700 PDT} FinishedAt:{Time:2016-09-05 17:38:23 -0700 PDT} ContainerID:docker://2fb7705cd594d2632012866889ba8c12afb07dac1c975965edea29cbd2c27469}",
    }
    pod 'different-node-wget' terminated with failure: &{ExitCode:1 Signal:0 Reason:Error Message: StartedAt:{Time:2016-09-05 17:38:13 -0700 PDT} FinishedAt:{Time:2016-09-05 17:38:23 -0700 PDT} ContainerID:docker://2fb7705cd594d2632012866889ba8c12afb07dac1c975965edea29cbd2c27469}
not to have occurred

@k8s-github-robot
Copy link
Author

[FLAKE-PING] @freehan

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

@freehan
Copy link
Contributor

freehan commented Sep 14, 2016

Closing this one. Reopen if it occurs.

@davidopp
Copy link
Member

@k8s-github-robot
Copy link
Author

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

Failed: [k8s.io] Networking [k8s.io] Granular Checks should function for pod communication between nodes {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/networking.go:267
Expected error:
    <*errors.errorString | 0xc8207ed720>: {
        s: "pod 'different-node-wget' terminated with failure: &{ExitCode:1 Signal:0 Reason:Error Message: StartedAt:{Time:2016-09-27 19:26:55 -0700 PDT} FinishedAt:{Time:2016-09-27 19:27:05 -0700 PDT} ContainerID:docker://42aec844c87674389f62d5cd2030d1144aee5d7b2254e42c8394d84f565e7837}",
    }
    pod 'different-node-wget' terminated with failure: &{ExitCode:1 Signal:0 Reason:Error Message: StartedAt:{Time:2016-09-27 19:26:55 -0700 PDT} FinishedAt:{Time:2016-09-27 19:27:05 -0700 PDT} ContainerID:docker://42aec844c87674389f62d5cd2030d1144aee5d7b2254e42c8394d84f565e7837}
not to have occurred

@k8s-github-robot
Copy link
Author

https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gci-gce-release-1.4/436/

Failed: [k8s.io] Networking [k8s.io] Granular Checks should function for pod communication between nodes {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/networking.go:271
Expected error:
    <*errors.errorString | 0xc820c70ca0>: {
        s: "pod 'different-node-wget' terminated with failure: &{ExitCode:1 Signal:0 Reason:Error Message: StartedAt:2016-09-29 12:34:40 -0700 PDT FinishedAt:2016-09-29 12:34:40 -0700 PDT ContainerID:docker://aad38392c8eb263e7eeedea98e18f132b9c2eb8f9217b03e7df59063669c2d68}",
    }
    pod 'different-node-wget' terminated with failure: &{ExitCode:1 Signal:0 Reason:Error Message: StartedAt:2016-09-29 12:34:40 -0700 PDT FinishedAt:2016-09-29 12:34:40 -0700 PDT ContainerID:docker://aad38392c8eb263e7eeedea98e18f132b9c2eb8f9217b03e7df59063669c2d68}
not to have occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/networking.go:270

@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 Sep 29, 2016
@k8s-github-robot
Copy link
Author

[FLAKE-PING] @freehan

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/297/

Failed: [k8s.io] Networking [k8s.io] Granular Checks should function for pod communication between nodes {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/networking.go:267
Expected error:
    <*errors.errorString | 0xc820a79660>: {
        s: "pod 'different-node-wget' terminated with failure: &{ExitCode:1 Signal:0 Reason:Error Message: StartedAt:{Time:2016-09-29 16:42:28 -0700 PDT} FinishedAt:{Time:2016-09-29 16:42:38 -0700 PDT} ContainerID:docker://2d5c501e3522372192265810902c4b59ad49182ad20e244df58bb016d8d3ab64}",
    }
    pod 'different-node-wget' terminated with failure: &{ExitCode:1 Signal:0 Reason:Error Message: StartedAt:{Time:2016-09-29 16:42:28 -0700 PDT} FinishedAt:{Time:2016-09-29 16:42:38 -0700 PDT} ContainerID:docker://2d5c501e3522372192265810902c4b59ad49182ad20e244df58bb016d8d3ab64}
not to have occurred

@calebamiles
Copy link
Contributor

calebamiles commented Nov 3, 2016

@freehan any updates on this issue? there was a failure posted to testgrid as late as 1 November 2016

@k8s-github-robot
Copy link
Author

https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gci-gce-release-1.4/2116/

Failed: [k8s.io] Networking [k8s.io] Granular Checks should function for pod communication between nodes {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/networking.go:271
Expected error:
    <*errors.errorString | 0xc82085cfd0>: {
        s: "pod 'different-node-wget' terminated with failure: &{ExitCode:1 Signal:0 Reason:Error Message: StartedAt:2016-11-03 02:59:53 -0700 PDT FinishedAt:2016-11-03 02:59:53 -0700 PDT ContainerID:docker://9251f04248345b16c6aa4564182a5a017c0ffb6607fdac4fd5983381d90f6923}",
    }
    pod 'different-node-wget' terminated with failure: &{ExitCode:1 Signal:0 Reason:Error Message: StartedAt:2016-11-03 02:59:53 -0700 PDT FinishedAt:2016-11-03 02:59:53 -0700 PDT ContainerID:docker://9251f04248345b16c6aa4564182a5a017c0ffb6607fdac4fd5983381d90f6923}
not to have occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/networking.go:270

@fredjean
Copy link
Contributor

fredjean commented Nov 3, 2016

@calebamiles I think that you meant to poke @freehan instead of me.

@k8s-github-robot
Copy link
Author

[FLAKE-PING] @freehan

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

3 similar comments
@k8s-github-robot
Copy link
Author

[FLAKE-PING] @freehan

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

@k8s-github-robot
Copy link
Author

[FLAKE-PING] @freehan

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

@k8s-github-robot
Copy link
Author

[FLAKE-PING] @freehan

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

@calebamiles calebamiles added this to the v1.5 milestone Nov 11, 2016
@k8s-github-robot
Copy link
Author

[FLAKE-PING] @freehan

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

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

[FLAKE-PING] @freehan

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

@k8s-github-robot
Copy link
Author

[FLAKE-PING] @freehan @jayunit100

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

@jayunit100
Copy link
Member

Possibly a retry on this would fix it? ill dig shortly

                for _, test := range tests {
                        By(fmt.Sprintf("testing: %s", test.path))
                        data, err := f.ClientSet.Core().RESTClient().Get().
                                AbsPath(test.path).
                                DoRaw()
                        if err != nil {
                                framework.Failf("Failed: %v\nBody: %s", err, string(data))
                        }
                }

@saad-ali
Copy link
Member

Thanks @jayunit100! Please let us know by EOD Friday if this issue should be considered a blocker or non-blocker for the 1.5 release.

Assigning @matchstick since @freehan is OOF.

@jayunit100
Copy link
Member

Hmmm i looked a little more. I think this could be just an infra flake in disguise.

@jayunit100
Copy link
Member

i think all the flake logs here are not useful

  • line 50 is an infra flake, its just happening because the api routes arent set up well.
  • line 267/261 are all old code , i think, from before some refactorings occured ?

I say close , there isnt a common thread here. some of the stuff that is being reported is clearly just an infra flake , for example (Oct 31 10:40:44.761: Unable to connect/talk to the internet: Get http://google.com: dial tcp [2607:f8b0:4001:c05::64]:80: connect: network is unreachable).

@saad-ali
Copy link
Member

I say close , there isnt a common thread here. some of the stuff that is being reported is clearly just an infra flake

Ack. Closing issue

k8s-github-robot pushed a commit that referenced this issue Nov 30, 2016
Automatic merge from submit-queue

Skip rather than fail networking tests on single node

**What this PR does / why we need it**:

Needed for the general e2e tidying we need to do for flakey slow tests, imo pre 1.5, see #31402  and so on.

**Which issue this PR fixes** * 

Dont fail multinode tests if on a single node cluster, skip instead.
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/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now.
Projects
None yet
Development

No branches or pull requests

8 participants