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

Extended.[networking] services when using a plugin that isolates namespaces by default should prevent connections to pods in different namespaces on the same node via service IPs #14241

Closed
mfojtik opened this issue May 18, 2017 · 1 comment
Assignees
Labels
component/networking kind/test-flake Categorizes issue or PR as related to test flakes. priority/P1

Comments

@mfojtik
Copy link
Contributor

mfojtik commented May 18, 2017

Seen here: https://ci.openshift.redhat.com/jenkins/job/merge_pull_request_origin/689/testReport/junit/(root)/Extended/_networking__services_when_using_a_plugin_that_isolates_namespaces_by_default_should_prevent_connections_to_pods_in_different_namespaces_on_the_same_node_via_service_IPs/

logs:

/data/src/github.com/openshift/origin/_output/local/go/src/github.com/openshift/origin/test/extended/networking/services.go:42
Expected error:
    <*errors.errorString | 0xc421c00a10>: {
        s: "Failed to get endpoints for e2e-tests-net-services1-jk963/service-mf46q",
    }
    Failed to get endpoints for e2e-tests-net-services1-jk963/service-mf46q
not to have occurred
/data/src/github.com/openshift/origin/_output/local/go/src/github.com/openshift/origin/test/extended/networking/util.go:147
@danwinship
Copy link
Contributor

dup of #14197

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/networking kind/test-flake Categorizes issue or PR as related to test flakes. priority/P1
Projects
None yet
Development

No branches or pull requests

4 participants