-
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
openshift-sdn failed health check with "link not found" on GCP, failed test #18317
Labels
component/networking
kind/bug
Categorizes issue or PR as related to a bug.
kind/test-flake
Categorizes issue or PR as related to test flakes.
priority/P1
sig/networking
Comments
smarterclayton
added
kind/bug
Categorizes issue or PR as related to a bug.
component/networking
kind/test-flake
Categorizes issue or PR as related to test flakes.
sig/networking
labels
Jan 28, 2018
smarterclayton
changed the title
Connectivity never established between exec pod and another pod in namespace
openshift-sdn failed health check with "link down"
Jan 28, 2018
Is this the health check being too aggressive, or a symptom of a bigger problem on the node? |
smarterclayton
changed the title
openshift-sdn failed health check with "link down"
openshift-sdn failed health check with "link down" on GCP, failed test
Jan 28, 2018
on node ci-prtest-5a37c28-15216-ig-n-t1xb |
danwinship
changed the title
openshift-sdn failed health check with "link down" on GCP, failed test
openshift-sdn failed health check with "link not found" on GCP, failed test
Feb 2, 2018
openshift-merge-robot
added a commit
that referenced
this issue
Feb 2, 2018
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
component/networking
kind/bug
Categorizes issue or PR as related to a bug.
kind/test-flake
Categorizes issue or PR as related to test flakes.
priority/P1
sig/networking
https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/18229/test_pull_request_origin_extended_conformance_gce/15151/#conformanceareanetworkingfeaturerouter-openshift-routers-the-haproxy-router-should-serve-the-correct-routes-when-scoped-to-a-single-namespace-and-label-set-suiteopenshiftconformanceparallel
exec pod was trying to curl the router (which was up) but wasn't able to create a connection.
Router was up a few seconds after the exec pod was created, but it was never able to connect to the destination pod:
Logs from router
The s4sd node ovs health check failed immediately after the router started:
@openshift/sig-networking @openshift/networking
The text was updated successfully, but these errors were encountered: