Workaround: delete the Kibana pod and wait for the new pod to start, then login Kibana
Setting severity to low since a workaround has been provided
Moving to UpcomingSprint as unlikely to be resolved by EOS
@Qiaoling, can you please provide the logs for CLO when recreating this?
Unlikely to resolve EOS. Moving to UpcomingSprint
Waiting errata metadata images.
Verified on clusterlogging.4.4.0-202008100806.p0
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 (OpenShift Container Platform 4.4.17 extras 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/RHBA-2020:3336