Crio and kubelet services are stuck in "dead" status and are unable to start in OCP 4

Issue

• Crio and kubelet services stay in dead status when trying to start in OCP 4 nodes:

# sudo systemctl status crio

● crio.service - Open Container Initiative Daemon
 20-nodenet.conf
   Active: inactive (dead) <--

# sudo systemctl status kubelet

● kubelet.service - Kubernetes Kubelet
  Drop-In: /etc/systemd/system/kubelet.service.d
           └─10-mco-default-madv.conf, 20-logging.conf, 20-nodenet.conf
   Active: inactive (dead) <-- 

• Nodes stay as NotReady since kubelet and crio are not starting.
• Rebooting the affected nodes doesn't fix the issue.