Created attachment 1601600 [details] YAML manifest to reproduce issue Description of problem: If a pod has multiple containers, the pod gets marked as "Completed" in the web interface after the first container finishes, even if the other container(s) is still running. That was first noticed on the openshift api.ci cluster (origin CI), and I have been able to easily reproduce on a local openshift 3.11 cluster. Version-Release number of selected component (if applicable): 3.11 How reproducible: Always able to reproduce Steps to Reproduce: 1. Create a pod with 2 containers, one that finishes significantly earlier than the other. See attached "test.yaml" for a simple busybox example where 1 container runs for 1 second and the other for 100. 2. Check the pod status in the web interface and the CLI (get pods) after the first container finishes, but before the second one finishes Actual results: Web interface shows the status of the pod as "Completed" while the CLI lists it as "Running" Expected results: Both the web interface and CLI show the status as "Running".
Created attachment 1601601 [details] Screenshot of web interface showing "Completed" status with containers still running
I have tested this against the latest nightly openshift origin 4.2 and the problem exists there as well
Updated version and name to indicate that is occurs on openshift 4.2
Do you happen to have the YAML for the pods or a reproducer?
There is a YAML manifest attached to this bug that should reproduce the problem.
Thanks, I see it now. Confirmed openshift/console/pull/2402 fixes the issue.
Created attachment 1606816 [details] Now the pod is Running when one of the containers is Finished and the other is still Running.
Verified on 4.2.0-0.nightly-2019-08-21-210916 See the screenshot from attachment.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:2922