Created attachment 1868215 [details] Replicaset Logs Not shown Description of the problem: Replicasets in Topology doesnt show the console logs of the pods. Instead, it gives an error saying that : Error querying resource logs: No pods found Release version: 2.5 Operator snapshot version: 2.5.0-DOWNSTREAM-2022-03-23-01-06-05 OCP version: 4.10.3 Browser Info: Firefox Steps to reproduce: 1. Login to ACM console 2. Create a subscription based application 3. Once deployed successfully, go to the Topology tab 4. Click on the Replicaset resource to open the sidebar 5. Click on Logs on the sidebar Actual results: User sees the following: Error querying resource logs: No pods found Expected results: User should see a console with pod logs Additional info:
G2Bsync 1080710186 comment fxiang1 Mon, 28 Mar 2022 14:15:46 UTC G2Bsync With John's changes for Topology drilldown https://github.com/stolostron/backlog/issues/19364, there was a design change which is to display the Pod node now for all resources that deploy a Pod resource. So the Logs tab should be accessed on the Pod node instead. I will remove the Logs tab for Replicasets and other resources that deploy Pods. With that said, I did find bugs where other resources are not displaying the Pod node so I'm also going to fix that in this issue since it's related.
Verified in 2.5.0-DOWNSTREAM-2022-04-20-06-50-05 on Firefox 91.8.0esr (64-bit)
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.
Bug 2068304 refers to an issue related to the application lifecycle and the absence of logs in the console for replicasets in the topology view. However, without additional context or details, it is challenging to provide a specific solution or further https://www-prepaidgiftbalance.com/ information about the bug. To better assist you, please provide more details, such as the platform or technology stack you are using, any error messages or symptoms you are experiencing, and any relevant configuration or steps to reproduce the issue.
Hello, ReplicaSets manage the desired number of pod replicas in Kubernetes, ensuring high availability. However, in the Topology aware log console the logs of individual replicas are not visible, making it difficult to monitor and troubleshoot specific instances. https://www.surveyzo.com/official-partycityfeedback-com/
Thanksa for sharing this, this is amazing. i like it. https://www.subwaygiftcardbalance.online/