Created attachment 1852109 [details]
Description of problem:
The status of container is not consistent on Container details and pod details page
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create a resource as below shown
- name: crash-app
2. Login OCP, navigate to Pods details page, check the state that shown under containers section
3. Click on the name of the container
4. Check the status that behind the name, verify if it is as same as the state that shown on Step 2
Status text and icon is showing Running on container details page while pod details page shows container state ‘waiting`
The status of container could consistent on Container details and pod details page
Looks like we are using different methods to get the status of the container in it's details page PageHeading vs the ContainerDetails components. Thats why we see the inconsistency.
We should be passing custom 'getResourceStatus' function to the 'PageHeading' component in https://github.com/openshift/console/blob/master/frontend/public/components/container.tsx#L396-L408
otherwise the 'PageHeading' components goes with the default 'status.phase' field, based on https://github.com/openshift/console/blob/master/frontend/public/components/utils/headings.tsx#L106
I think we should be using 'getContainerStatus' instead https://github.com/openshift/console/blob/master/frontend/public/module/k8s/container.ts#L29
Tim let me know if you have any questions.
This bug has been verified on payload 4.11.0-0.nightly-2022-03-04-063157
Follow the 'Steps to Reproduce' on comment1 to do the verification.
The state of container could consistent on Container details page and pod details -> containers section -> state column
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 (Important: OpenShift Container Platform 4.11.0 bug fix and security update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.