In RHOCP 3.11 master-api pod from kube-system project is in crashloopbackoff state

Issue

• master-api pod is crashing on one master node while it is running fine on other 2 as shown below:

$ oc get pods -n kube-system
NAME                                            READY     STATUS             RESTARTS   AGE
master-api.node1.hostname.example.com            1/1       Running            15313      6d
master-api.node2.hostname.example.com            0/1       CrashLoopBackOff   14167      12h
master-api.node3.hostname.example.com            1/1       Running            4          12h
master-controllers.node1.hostname.example.com    1/1       Running            1958       8h
master-controllers.node2.hostname.example.com    1/1       Running            2986       12h
master-controllers.node3.hostname.example.com    1/1       Running            40         12h
master-etcd.node1.hostname.example.com           1/1       Running            3          8h
master-etcd.node2.hostname.example.com           1/1       Running            2          23h
master-etcd.node3.hostname.example.com           1/1       Running            2          23h

• master-api pod logs from node node2.hostname.example.com shows following error message:

1 reflector.go:136] k8s.io/kubernetes/pkg/client/informers/informers_generated/internalversion/factory.go:129: Failed to list *scheduling.PriorityClass: Get https://master-api-node2.hostname.example.com:8443/apis/scheduling.k8s.io/v1beta1/priorityclasses?limit=500&resourceVersion=0: x509: certificate is valid for kubernetes, kubernetes.default, kubernetes.default.svc, kubernetes.default.svc.cluster.local, master-api-node2.hostname.example.com,master-api1,openshift, openshift.default, openshift.default.svc, openshift.default.svc.cluster.local, 10.100.x,x 172.30.x.x, 192.168.x.x, not master-api-node2.hostname.example.com