Description of problem: When viewing openshift-apiserver, kube-apiserver or oauth-apiserver component logs on Master node, console will show a transient message 'No log files exist' and finally shows 'No log file selected' suggesting user to select a log file Version-Release number of selected component (if applicable): 4.9.0-0.nightly-2021-09-06-055314 How reproducible: Always Steps to Reproduce: 1. cluster admin user view Master node logs via Compute -> Nodes -> click on one Master node -> click 'Logs' tab 2. By default, console shows 'journal' log, click the resource dropdown to view other component logs such as openshift-apiserver, kube-apiserver or oauth-apiserver Actual results: 2. before the logs are loaded completely, we can see a 'No log files exist' flashing and finally we show 'No log file selected' to force user select a log file Expected results: 2. before loading is finished, we should better just show loading until everything is fetched Additional info:
now a loading icon is shown on the page before we finally show "No log files exist" or "No log file selected". Verified on 4.10.0-0.nightly-2021-09-21-181111
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 (Moderate: OpenShift Container Platform 4.10.3 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:0056