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

Flaky Test_ServiceLoadBalancerDisableAllocateNodePorts integration test #109785

Closed
sanposhiho opened this issue May 4, 2022 · 7 comments
Closed

Flaky Test_ServiceLoadBalancerDisableAllocateNodePorts integration test #109785

sanposhiho opened this issue May 4, 2022 · 7 comments
Labels
kind/flake Categorizes issue or PR as related to a flaky test. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. sig/network Categorizes an issue or PR as relevant to SIG Network.

Comments

@sanposhiho
Copy link
Member

Which jobs are flaking?

pull-kubernetes-integration

Which tests are flaking?

Test_ServiceLoadBalancerDisableAllocateNodePorts

Since when has it been flaking?

unknown

Testgrid link

https://testgrid.k8s.io/presubmits-kubernetes-blocking#pull-kubernetes-integration&include-filter-by-regex=Test_ServiceLoadBalancerDisableAllocateNodePorts

Reason for failure (if possible)

panic due to timeout(10m)

panic: test timed out after 10m0s

https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/109478/pull-kubernetes-integration/1521769536443912192

Anything else we need to know?

No response

Relevant SIG(s)

/sig
@sanposhiho sanposhiho added the kind/flake Categorizes issue or PR as related to a flaky test. label May 4, 2022
@k8s-ci-robot k8s-ci-robot added needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels May 4, 2022
@k8s-ci-robot
Copy link
Contributor

@sanposhiho: 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.

@sanposhiho sanposhiho mentioned this issue May 4, 2022
Merged
@alculquicondor
Copy link
Member

More of these ones @aojea

@alculquicondor
Copy link
Member

/sig network
?

@k8s-ci-robot k8s-ci-robot added sig/network Categorizes an issue or PR as relevant to SIG Network. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels May 4, 2022
@aojea
Copy link
Member

aojea commented May 4, 2022

/cc
:/

@thockin
Copy link
Member

thockin commented May 26, 2022

Now that we're back from KubeCon...

@aojea
Copy link
Member

aojea commented May 26, 2022

/close

this was a problem on the integration framework that was already solved

https://storage.googleapis.com/k8s-triage/index.html?pr=1&job=integration&test=ServiceLoadBalancerDisableAllocateNodePorts

@k8s-ci-robot
Copy link
Contributor

@aojea: Closing this issue.

In response to this:

/close

this was a problem on the integration framework that was already solved

https://storage.googleapis.com/k8s-triage/index.html?pr=1&job=integration&test=ServiceLoadBalancerDisableAllocateNodePorts

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
Assignees
No one assigned
Labels
kind/flake Categorizes issue or PR as related to a flaky test. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. sig/network Categorizes an issue or PR as relevant to SIG Network.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@alculquicondor @thockin @aojea @k8s-ci-robot @sanposhiho