On Openshift 4.12, scheduler extender is sometimes stuck in not ready status

[CraneShiEMC]

Describe the bug
On Openshift 4.12, sometimes, the readiness of the scheduler extender cannot be updated with the latest status and is stuck in not ready status.

Environment (please complete the following information):
Openshift 4.12

To Reproduce
The issue sometimes occurs during normal installation of CSI.

Expected behavior
The readiness check of the scheduler extender should reflect the latest status. The readiness of scheduler extender pod should turn to be ready if the secondary scheduler is ready and csi-baremetal-scheduler config was successfully applied to the secondary scheduler.

Screenshots

[root@servicenode se-readiness-fail]# kubectl get pods -o wide
NAME                                            READY   STATUS    RESTARTS   AGE   IP              NODE                         NOMINATED NODE   READINESS GATES
csi-baremetal-controller-96d7485dc-6ln4j        4/4     Running   0          58m   192.168.6.165   worker3.ocp4.dakotakai.com   <none>           <none>
csi-baremetal-node-8pf7f                        4/4     Running   0          58m   192.168.3.142   worker2.ocp4.dakotakai.com   <none>           <none>
csi-baremetal-node-controller-dd649d99c-t82xt   1/1     Running   0          58m   192.168.5.163   worker1.ocp4.dakotakai.com   <none>           <none>
csi-baremetal-node-d99xs                        4/4     Running   0          58m   192.168.1.124   master2.ocp4.dakotakai.com   <none>           <none>
csi-baremetal-node-jxqvf                        4/4     Running   0          58m   192.168.5.164   worker1.ocp4.dakotakai.com   <none>           <none>
csi-baremetal-node-k6c4f                        4/4     Running   0          58m   192.168.0.149   master0.ocp4.dakotakai.com   <none>           <none>
csi-baremetal-node-qvzqg                        4/4     Running   0          58m   192.168.4.59    worker0.ocp4.dakotakai.com   <none>           <none>
csi-baremetal-node-vfwk7                        4/4     Running   0          58m   192.168.6.166   worker3.ocp4.dakotakai.com   <none>           <none>
csi-baremetal-node-zfrbg                        4/4     Running   0          58m   192.168.2.159   master1.ocp4.dakotakai.com   <none>           <none>
csi-baremetal-operator-77d59bf65-rh9lg          1/1     Running   0          58m   192.168.5.162   worker1.ocp4.dakotakai.com   <none>           <none>
csi-baremetal-se-f986m                          0/1     Running   0          58m   10.236.66.170   master0.ocp4.dakotakai.com   <none>           <none>
csi-baremetal-se-jbxxf                          0/1     Running   0          58m   10.236.66.171   master1.ocp4.dakotakai.com   <none>           <none>
csi-baremetal-se-ttb2l                          0/1     Running   0          58m   10.236.66.172   master2.ocp4.dakotakai.com   <none>           <none>

Additional context
Add any other context about the problem here.