origin: test/end-to-end/core.sh:376: executing 'oc logs kubectl-with-token' expecting success and text 'Using in-cluster configuration': the output content test failed

Seen in https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin_integration/10167/consoleFull:

FAILURE after 0.223s: test/end-to-end/core.sh:375: executing 'oc logs kubectl-with-token' expecting success and text 'Using in-cluster configuration': the output content test failed
Standard output from the command:
NAME                 READY     STATUS    RESTARTS   AGE
kubectl-with-token   1/1       Running   0          5s

About this issue

Original URL
State: closed
Created 7 years ago
Comments: 72 (72 by maintainers)

Commits related to this issue

Re-enable e2e tests that were failing due to #12558 — committed to soltysh/origin by soltysh 7 years ago
Re-enable e2e tests that were failing due to #12558 — committed to soltysh/origin by soltysh 7 years ago
Re-enable e2e tests that were failing due to #12558 — committed to soltysh/origin by soltysh 7 years ago
Re-enable e2e tests that were failing due to #12558 — committed to soltysh/origin by soltysh 7 years ago
Re-enable e2e tests that were failing due to #12558 — committed to soltysh/origin by soltysh 7 years ago
Re-enable e2e tests that were failing due to #12558 — committed to soltysh/origin by soltysh 7 years ago
Re-enable e2e tests that were failing due to #12558 — committed to soltysh/origin by soltysh 7 years ago
Re-enable e2e tests that were failing due to #12558 — committed to soltysh/origin by soltysh 7 years ago
Re-enable e2e tests that were failing due to #12558 — committed to soltysh/origin by soltysh 7 years ago
Re-enable e2e tests that were failing due to #12558 — committed to soltysh/origin by soltysh 7 years ago
Re-enable e2e tests that were failing due to #12558 — committed to soltysh/origin by soltysh 7 years ago
Re-enable e2e tests that were failing due to #12558 — committed to soltysh/origin by soltysh 7 years ago
Merge pull request #3753 from soltysh/issue12558 Automatic merge from submit-queue Increase rate limiting in journald.conf @sdodson ptal, this is to address issues from https://github.com/openshift... — committed to openshift/openshift-ansible by openshift-merge-robot 7 years ago

Most upvoted comments

this is rapidly becoming one of those cases where if we don’t have a fix in the merge queue, we should have a PR to disable the test in the merge queue.

bparees on Jan 21, 2017

Yes when I dream, my imagination comes up with P1 flakes 😃

stevekuznetsov on Jan 20, 2017