Bug 2078973
| Summary: | Crashed pod is marked with success in Topology | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Advanced Cluster Management for Kubernetes | Reporter: | Thuy Nguyen <thnguyen> | ||||
| Component: | Console | Assignee: | Feng Xiang <fxiang> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Xiang Yin <xiyin> | ||||
| Severity: | medium | Docs Contact: | Christopher Dawson <cdawson> | ||||
| Priority: | unspecified | ||||||
| Version: | rhacm-2.5 | CC: | dho, dhuynh, fxiang, huichen, jwakely, yuhe | ||||
| Target Milestone: | --- | Flags: | bot-tracker-sync:
rhacm-2.5+
|
||||
| Target Release: | rhacm-2.5 | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2022-06-09 02:11:44 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: | |||||||
| Attachments: |
|
||||||
G2Bsync 1117536104 comment thuyn-581 Wed, 04 May 2022 16:06:47 UTC G2BSync - Validated on ACM 2.5.0-DOWNSTREAM-2022-05-02-16-00-32. 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: Red Hat Advanced Cluster Management 2.5 security updates, images, and bug fixes), 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:4956 This comment was flagged a spam, view the edit history to see the original text if required. This comment was flagged a spam, view the edit history to see the original text if required. Thanks for the information, I will try to figure it out for more. Keep sharing such informative post keep suggesting such post. https://www.allieduniversalehub.net/ kubectl describe pod [your-pod-name] will show a Last State which gives you a high level indication. To see what happened on the pod before it restarted, use kubectl logs your-pod-name --previous https://www.myccpay.fyi/ Thanks i fixed it thanks for inform. https://www.upsers.app/ Enjoyed reading the article above, really explains everything in detail, and the article is very interesting and effective. https://www.doglikesbest.com/ |
Created attachment 1875112 [details] Topology details Description of the problem: Crashed pod is marked with success in Topology Release version: Operator snapshot version: 2.5.0-DOWNSTREAM-2022-04-21-01-26-54 OCP version: 4.10.11 Browser Info: Steps to reproduce: 1. Create application set and deploy onto managed cluster 2. Check Topology details Actual results: Topology shows success status for pod which crashes Expected results: Additional info: