Okd: Node status NotReady after rebooting master node

[achilles-git]

Describe the bug

I am using OKD 4.5 with FCOS ,recently I rebooted a master node and now the master node status is NotReady.
i ran the $oc describe master1.node.com and output was kubelet stopped posting status.
also I tried to check if there are any pending CSR requests by $oc get csr found that there are csr requests from system:node:localhost ,but I have no node named localhost in the cluster.(kubelet might have started before the hostname stabilizes)
also restarting kubelet $systemctl restart kubelet is not helping
Version

Server Version: 4.5.0-0.okd-2020-07-29-070316

How reproducible

Restarting the master node
Log bundle

attaching kubelet logs from master1 for reference

master1.log.zip

[behnm]

I have the same issue.
Does not have any solution ?

[achilles-git]

In my case, i had to delete the node resource and add it back to the cluster

[vrutkovs]

No log bundle provided, closing

[dcdh]

In my case, i had to delete the node resource and add it back to the cluster

How did you did it ?

[achilles-git]

@dcdh
you can delete a node by oc delete node node_name

and the new node will be automatically added to cluster when you bootup(you just have to approve csr)