Flake: github.com/openshift/origin/test/end-to-end/core.test/end-to-end/core.sh:389

[tnozicka]

github.com/openshift/origin/test/end-to-end/core.test/end-to-end/core.sh:389: executing 'cat '/data/src/github.com/openshift/origin/_output/scripts/test-end-to-end/logs/cli-with-token2.log'' expecting success and text 'system:serviceaccount:test:default' (from github.com_openshift_origin_test_end-to-end_core)

https://ci.openshift.redhat.com/jenkins/job/merge_pull_request_origin/1143/consoleFull

Stacktrace

=== BEGIN TEST CASE ===
test/end-to-end/core.sh:389: executing 'cat '/data/src/github.com/openshift/origin/_output/scripts/test-end-to-end/logs/cli-with-token2.log'' expecting success and text 'system:serviceaccount:test:default'
FAILURE after 0.016s: test/end-to-end/core.sh:389: executing 'cat '/data/src/github.com/openshift/origin/_output/scripts/test-end-to-end/logs/cli-with-token2.log'' expecting success and text 'system:serviceaccount:test:default': the output content test failed
Standard output from the command:
If you don't see a command prompt, try pressing enter.
I0627 04:47:26.039053       1 merged_client_builder.go:123] Using in-cluster configuration
I0627 04:47:26.041609       1 merged_client_builder.go:123] Using in-cluster configuration
I0627 04:47:26.076348       1 cached_discovery.go:134] failed to write cache to /root/.kube/172.30.0.1_443/servergroups.json due to mkdir /root/.kube: permission denied
I0627 04:47:26.077108       1 merged_client_builder.go:123] Using in-cluster configuration

There was no error output from the command.
=== END TEST CASE ===

[pweil-]

@fabianofranz actually, this looks like it may be another instance of the --attach issues we've seen in the past like #12558 which was supposedly fixed in #13669 but maybe just for test-end-to-end-docker.sh.

@soltysh PTAL.

[soltysh]

@pweil- correct, this is enabled only for test-end-to-docker.sh, but that's the default we'll fallback to when docker is installed, which is what happens in our CI (look for ++ Docker is installed, running hack/test-end-to-end-docker.sh instead). I'm worried this is back, but at this point in time I have no idea why, since the journald rate limiting is off (look for Turning off journald limits). It's not a blocker for 3.6, but I'll be paying attention, since it looks like we're hitting it more and more often recently 😞

[soltysh]

After IRC discussion with @pweil- I'll lower the prio. I need logs to verify what's going on and none of the current instances has those. It won't block the release in any way and I'll keep my eye open for it.

[simo5]

flaked on #14745 too