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

Failure cluster [25f9dd15...] e2e suite [It] [sig-network] Services should serve endpoints on same port and different protocols #116527

Closed
pacoxu opened this issue Mar 13, 2023 · 6 comments
Labels
sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. sig/network Categorizes an issue or PR as relevant to SIG Network. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@pacoxu
Copy link
Member

pacoxu commented Mar 13, 2023

Failure cluster 25f9dd15fbca0ddd7a02

Error text:
[FAILED] Timed out after 30.000s.
Expected
    <nil>: nil
not to be nil
In [It] at: test/e2e/network/service.go:3703 @ 03/12/23 06:45:16.6

Recent failures:

2023/3/13 03:49:12 e2e-kops-gce-latest
2023/3/13 01:03:11 e2e-kops-scenario-arm64
2023/3/13 00:49:11 e2e-kops-gce-latest
2023/3/12 21:49:15 e2e-kops-gce-latest
2023/3/12 21:06:11 e2e-kops-scenario-terraform

/kind failing-test

/sig network

The test was added in #116333
/cc @aojea

@k8s-ci-robot k8s-ci-robot added kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. 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 13, 2023
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

@aojea
Copy link
Member

aojea commented Mar 13, 2023

Legit failures if those jobs are using cilium, one is a known bug in cilium cilium/cilium#9207

and I fixed the other recently cilium/cilium#24202

@aojea
Copy link
Member

aojea commented Mar 13, 2023

/sig cluster-lifecycle
/remove-kind failing-test
/kind failing-job

/cc @justinsb

@k8s-ci-robot k8s-ci-robot added sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. and removed kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. labels Mar 13, 2023
@k8s-ci-robot
Copy link
Contributor

@aojea: The label(s) kind/failing-job cannot be applied, because the repository doesn't have them.

In response to this:

/sig cluster-lifecycle
/remove-kind failing-test
/kind failing-job

/cc @justinsb

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.

@thockin thockin 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 16, 2023
@aojea
Copy link
Member

aojea commented May 24, 2023

@k8s-ci-robot
Copy link
Contributor

@aojea: Closing this issue.

In response to this:

/close

https://storage.googleapis.com/k8s-triage/index.html?test=same%20port%20and%20different%20protocols

it was skipped in kops kubernetes/kops#15240

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. sig/network Categorizes an issue or PR as relevant to SIG Network. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests

4 participants