Skip to content

test/end-to-end/core:183: oc status output fragmented across oc run --attach #9309

@stevekuznetsov

Description

@stevekuznetsov

Seeing this in AWS-based image.

$ oc run cli-with-token --attach --image=openshift/origin:${TAG} --restart=Never -- cli status --loglevel=4 > ${LOG_DIR}/cli-with-token.log 2>&1
...
Jun 13 15:59:11 Running test/end-to-end/core.sh:183: executing 'cat '/tmp/openshift/test-end-to-end-docker//logs/cli-with-token.log'' expecting success and text 'In project test'...
Jun 13 15:59:11 FAILURE after 0.010s: test/end-to-end/core.sh:183: executing 'cat '/tmp/openshift/test-end-to-end-docker//logs/cli-with-token.log'' expecting success and text 'In project test': the output content test failed
Jun 13 15:59:11 Standard output from the command:
Jun 13 15:59:11 Waiting for pod test/cli-with-token to be running, status is Pending, pod ready: false
Jun 13 15:59:11 I0613 19:59:08.888906       1 factory.go:129] Using in-cluster configuration
Jun 13 15:59:11 I0613 19:59:08.916543       1 factory.go:129] Using in-cluster configuration
Jun 13 15:59:11 I0613 19:59:08.918458       1 factory.go:129] Using in-cluster configuration
Jun 13 15:59:11 pod/cli-with-token runs openshift/origin:4148579
Jun 13 15:59:11 2 warnings identified, use 'oc status -v' to see details.
Jun 13 15:59:11 
Jun 13 15:59:11 There was no error output from the command.

We see some of the output from oc status ... but not all of it?

@deads2k @ncdc thoughts?

Metadata

Metadata

Assignees

Labels

component/clikind/test-flakeCategorizes issue or PR as related to test flakes.lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.priority/P2

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions