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

[Flaky test] [sig-network] Services should be able to change the type from ExternalName to NodePort [Conformance] #100133

Closed
tosi3k opened this issue Mar 11, 2021 · 3 comments
Assignees
Labels
kind/flake Categorizes issue or PR as related to a flaky test. sig/network Categorizes an issue or PR as relevant to SIG Network. sig/scalability Categorizes an issue or PR as relevant to SIG Scalability. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@tosi3k
Copy link
Member

tosi3k commented Mar 11, 2021

Which jobs are flaking:

ci-kubernetes-e2e-gce-scale-correctness

Which test(s) are flaking:

[sig-network] Services should be able to change the type from ExternalName to NodePort [Conformance]

Testgrid link:

https://testgrid.k8s.io/sig-scalability-gce#gce-master-scale-correctness

Reason for failure:

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:630
Mar 10 12:46:59.676: Unexpected error:
    <*errors.errorString | 0xc00ed4d100>: {
        s: "service is not reachable within 2m0s timeout on endpoint 10.40.7.231:30901 over TCP protocol",
    }
    service is not reachable within 2m0s timeout on endpoint 10.40.7.231:30901 over TCP protocol
occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/service.go:1351

Anything else we need to know:

Prow job URL with the failure: https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-kubernetes-e2e-gce-scale-correctness/1369619536927526912.

Another failure took place on Feb 22nd, although the reason for failure seems different: https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-kubernetes-e2e-gce-scale-correctness/1363821125104046080.

/sig scalability
/sig network

@tosi3k tosi3k added the kind/flake Categorizes issue or PR as related to a flaky test. label Mar 11, 2021
@k8s-ci-robot k8s-ci-robot added sig/scalability Categorizes an issue or PR as relevant to SIG Scalability. sig/network Categorizes an issue or PR as relevant to SIG Network. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Mar 11, 2021
@thejoycekung thejoycekung added this to New (no response yet) in CI Signal team (SIG Release) Mar 11, 2021
@aojea
Copy link
Member

aojea commented Mar 18, 2021

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Mar 18, 2021
@aojea
Copy link
Member

aojea commented May 11, 2021

@k8s-ci-robot
Copy link
Contributor

@aojea: Closing this issue.

In response to this:

/close
last failure was on Mar19
https://testgrid.k8s.io/sig-scalability-gce#gce-master-scale-correctness&width=5&include-filter-by-regex=ExternalName

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

CI Signal team (SIG Release) automation moved this from New (no response yet) to Observing (observe test failure/flake before marking as resolved) May 11, 2021
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. sig/network Categorizes an issue or PR as relevant to SIG Network. sig/scalability Categorizes an issue or PR as relevant to SIG Scalability. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
CI Signal team (SIG Release)
  
Observing (observe test failure/flake...
Development

No branches or pull requests

3 participants