Description of problem: Seems similar to an open BZ for 4.4: https://bugzilla.redhat.com/show_bug.cgi?id=1809593 Version-Release number of selected component (if applicable): OpenShift 4.3 How reproducible: Occurs periodically in customer's environment Actual results: [core@cp-2prqk-master-0 ~]$ oc get pods -A | grep -v Running | grep -v Completed NAMESPACE NAME READY STATUS RESTARTS AGE openshift-apiserver apiserver-24dz5 0/1 CrashLoopBackOff 1608 6d1h openshift-operator-lifecycle-manager packageserver-5866bccf76-g4jft 1/1 Terminating 0 3m44s Expected results: apiserver pod stability
what specific version of 4.3 is it happening in? A fix for this is coming in 4.3.18 (assuming it is the same issue as was in 4.4, which I believe to be the case)
This occurrence was on 4.3.12 - I'm sure they would be willing to test a backport on 4.3.18 if not update to 4.4.3
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:2129