You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The CI job deploys origin using cri-o as its container runtime and then it deploys aggregated logging stack. After successful deployment, it runs the logging PR tests where it sometimes hangs indefinitely on a command oc exec logging-fluentd-7hhgt -- date +%Z (the fluentd pod name can be different). It is possible to oc rsh to the pod and run any commands but running oc exec will hang for a command if it hanged previously at least once for any oc exec.
Description
The CI job deploys origin using cri-o as its container runtime and then it deploys aggregated logging stack. After successful deployment, it runs the logging PR tests where it sometimes hangs indefinitely on a command
oc exec logging-fluentd-7hhgt -- date +%Z
(the fluentd pod name can be different). It is possible tooc rsh
to the pod and run any commands but runningoc exec
will hang for a command if it hanged previously at least once for anyoc exec
.https://ci.openshift.redhat.com/jenkins/job/test_pull_request_origin_aggregated_logging_ansible_crio/7/console
Steps to reproduce the issue:
Describe the results you received:
oc exec
hangs indefinitellyDescribe the results you expected:
oc exec
not to hang and return the output of the commandAdditional information you deem important (e.g. issue happens only occasionally):
Output of
crio --version
:Additional environment details (AWS, VirtualBox, physical, etc.):
AWS - https://ci.openshift.redhat.com/jenkins/job/test_pull_request_origin_aggregated_logging_ansible_crio/
The exact same test suite passes when openshift is using docker
The text was updated successfully, but these errors were encountered: