-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Extended.[k8s.io] Services should be able to create a functioning NodePort service #13108
Comments
This is not #11016 because 2m < 5m. |
P1 until triaged |
Link is broken?
…On Mon, Mar 13, 2017 at 2:54 AM, Ben Parees ***@***.***> wrote:
https://ci.openshift.redhat.com/jenkins/job/test_pull_
request_origin_ehttps://ci.openshift.redhat.com/jenkins/
job/test_pull_request_origin_extended_conformance_gce/148/
testReport/junit/(root)/Extended/_k8s_io__Services_
should_be_able_to_create_a_functioning_NodePort_service/
xtended_conformance_gce/148/testReport/junit/(root)/
Extended/_k8s_io__Services_should_be_able_to_create_a_
functioning_NodePort_service/
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#13108 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABG_p357jZxPsfJwHLnah-hjIss11Etkks5rlOg5gaJpZM4MLhGp>
.
|
link upated, sorry. |
Hm... found an instance of this flake in a recent test_branch_origin_extended_conformance_gce:
The important bit there being |
Automatic merge from submit-queue (batch tested with PRs 18376, 18355). Move pod-namespace calls out of process As discussed in #15991, we need to move all operations in the pod's network namespace out of process, due to a golang issue that allows setns() calls in a locked thread to leak into other threads, causing random lossage as operations intended for the main network namespace end up running in other namespaces instead. (This is fixed in golang 1.10 but we need a fix before then.) Fixes #15991 Fixes #14385 Fixes #13108 Fixes #18317
https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin_gce/965/testReport/junit/(root)/Extended/_k8s_io__Services_should_be_able_to_create_a_functioning_NodePort_service/
Never seen this flake before (in roughly 600 runs), looks like the port never became available in 5 minutes. This is openshift default SDN setup
Very weird
The text was updated successfully, but these errors were encountered: