openshift / openshift/origin

Re-enable `oc run --attach` verifications once the docker logs api fix is vendored

Open
#11,240 26 comments 0 reactions 1 assignee View on GitHub

Nobody has claimed this yet.

component/restapi lifecycle/frozen priority/P2
Dominant language
Go
Stars
8.7k
Forks
4.8k
Avg merge
4d 10h
Merged PRs (30d)
53

Description

Running test/end-to-end/core.sh:331: executing 'cat '/tmp/openshift/test-end-to-end-docker//logs/cli-with-token.log'' expecting success and text 'In project test'...
SUCCESS after 0.016s: test/end-to-end/core.sh:331: executing 'cat '/tmp/openshift/test-end-to-end-docker//logs/cli-with-token.log'' expecting success and text 'In project test'
Standard output from the command:
Waiting for pod test/cli-with-token to be running, status is Pending, pod ready: false
Waiting for pod test/cli-with-token to be running, status is Pending, pod ready: false
I1005 22:44:47.756240       1 merged_client_builder.go:122] Using in-cluster configuration
I1005 22:44:47.789231       1 merged_client_builder.go:122] Using in-cluster configuration
I1005 22:44:47.792214       1 merged_client_builder.go:122] Using in-cluster configuration
I1005 22:44:47.792372       1 merged_client_builder.go:145] Using in-cluster namespace
In project test on server https://172.30.0.1:443
pod/cli-with-token runs openshift/origin:6cd347a
2 warnings identified, use 'openshift cli status -v' to see details.

There was no error output from the command.
Running test/end-to-end/core.sh:332: executing 'oc delete pod cli-with-token' expecting success...
SUCCESS after 0.289s: test/end-to-end/core.sh:332: executing 'oc delete pod cli-with-token' expecting success
Standard output from the command:
pod "cli-with-token" deleted

There was no error output from the command.
Running test/end-to-end/core.sh:334: executing 'cat '/tmp/openshift/test-end-to-end-docker//logs/cli-with-token2.log'' expecting success and text 'system:serviceaccount:test:default'...
FAILURE after 0.015s: test/end-to-end/core.sh:334: executing 'cat '/tmp/openshift/test-end-to-end-docker//logs/cli-with-token2.log'' expecting success and text 'system:serviceaccount:test:default': the output content test failed
Standard output from the command:
Waiting for pod test/cli-with-token-2 to be running, status is Pending, pod ready: false
Waiting for pod test/cli-with-token-2 to be running, status is Pending, pod ready: false
If you don't see a command prompt, try pressing enter.
Waiting for pod test/cli-with-token-2 to terminate, status is Running

There was no error output from the command.
[ERROR] PID 30321: hack/lib/cmd.sh:229: `return "${return_code}"` exited with status 1.
[INFO]      Stack Trace: 
[INFO]        1: hack/lib/cmd.sh:229: `return "${return_code}"`
[INFO]        2: test/end-to-end/core.sh:334: os::cmd::expect_success_and_text
[INFO]   Exiting with code 1.
[ERROR] PID 29510: hack/test-end-to-end-docker.sh:94: `${OS_ROOT}/test/end-to-end/core.sh` exited with status 1.
[INFO]      Stack Trace: 
[INFO]        1: hack/test-end-to-end-docker.sh:94: `${OS_ROOT}/test/end-to-end/core.sh`
[INFO]   Exiting with code 1.
[INFO] Stacked plot for log subset "iops" written to /tmp/openshift/test-end-to-end-docker//logs/iops.pdf
[INFO] Stacked plot for log subset "paging" written to /tmp/openshift/test-end-to-end-docker//logs/paging.pdf
[INFO] Stacked plot for log subset "cpu" written to /tmp/openshift/test-end-to-end-docker//logs/cpu.pdf
[INFO] Stacked plot for log subset "queue" written to /tmp/openshift/test-end-to-end-docker//logs/queue.pdf
[INFO] Stacked plot for log subset "memory" written to /tmp/openshift/test-end-to-end-docker//logs/memory.pdf

[FAIL] !!!!! Test Failed !!!!

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.