Node object is removed after being not ready for some time in vsphere

Issue

A node gets removed when it is NotReady for some time in vsphere, even when its VM has not been removed
```
$ oc get nodes|grep wrongnode
wrongnode.example.com     Ready, SchedulingDisabled   master   2y151d   v1.23.5+8471591
$ sleep $SOME_TIME
$ oc get nodes|grep wrongnode
$   
```
An example of issue that can cause the node to be not ready is the one described in this solution
Messages like the ones in "diagnostic steps" are seen in kube-controller-manager
If the node is recovered, it is listed again in oc get nodes

Red Hat OpenShift Container Platform 4 (RHOCP 4)
- 4.x
- vSphere UPI or IPI
- not baremetal UPI (even if installed on top of vSphere VMs)

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.