Bug 2042838
| Summary: | The status of container is not consistent on Container details and pod details page | ||||||
|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Xiyun Zhao <xiyuzhao> | ||||
| Component: | Management Console | Assignee: | Jakub Hadvig <jhadvig> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Xiyun Zhao <xiyuzhao> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 4.10 | CC: | aos-bugs, jhadvig, yapei | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 4.11.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | No Doc Update | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2022-08-10 10:43:03 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 2059800 | ||||||
| Attachments: |
|
||||||
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. Result: 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. https://access.redhat.com/errata/RHSA-2022:5069 |
Created attachment 1852109 [details] container(upon)_vs_pod(under)_state 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): 4.10 How reproducible: Always Steps to Reproduce: 1. Create a resource as below shown apiVersion: v1 kind: Pod metadata: name: crash-pod spec: containers: - name: crash-app image: quay.io/openshifttest/crashpod restartPolicy: Always 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 Actual results: Status text and icon is showing Running on container details page while pod details page shows container state ‘waiting` Expected results: The status of container could consistent on Container details and pod details page Additional info: