Checked on ocp 4.11 cluster with payload 4.11.0-0.nightly-2022-04-08-205307. 1. Go to a pod page (of which the container has been restarted), such as # oc get pod -n openshift-ingress-operator NAME READY STATUS RESTARTS AGE ingress-operator-7f4d75fb5d-h4gh5 2/2 Running 2 (11h ago) 11h 2. On log tab, download the previous log and current log, compare the context, there are correct for previous log and current log.
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: OpenShift Container Platform 4.11.0 bug fix and 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:5069