Description of problem: Use "View pod logs" instead of "View pod overview" is more direct for debugging, and "Use "View pod logs" should go to pod logs tab. Version-Release number of selected component (if applicable): 4.5.0-0.nightly-2020-05-12-065413 How reproducible: 100% Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Note: After offline discussion with Guohua we agreed to implement "View pod events" instead of "View pod logs" Main reason was that logs may be empty on some error cases ( e.g. pod container never come up ) while the evnets will hold debug helpful information.
Shouldn't we use "Pod" instead of "pod"?
Created attachment 1690269 [details] pod events link
Created attachment 1690467 [details] pod events
Created attachment 1690468 [details] vm events
Pod events and VM events looks the same pretty much, so "View Pod logs" should be better for it.
@Guahua, hi, We discussed that and agreed to use events: https://bugzilla.redhat.com/show_bug.cgi?id=1835092#c1 Will implement logs than :-)
verified on upstream 4.5 branch, commit 88b7689b0fb3dfc557d9e06dc509952b9233661e.
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-2020:2409