Pods struck in container creating state "cri-o configured with cgroupfs cgroup manager"

Issue

• Pods stuck in a container creating state in one of the worker nodes.
• SDN/OVS pods on the same node are also not running with an error as shown below.

<unknown>   Normal    Scheduled                pod/ovs-fl5mj   Successfully assigned openshift-sdn/ovs-fl5mj to <worker-node-example.com>
5s          Warning   FailedCreatePodSandBox   pod/ovs-fl5mj   Failed create pod sandbox: rpc error: code = Unknown desc = cri-o configured with cgroupfs cgroup manager, but received systemd slice as parent: /kubepods.slice/kubepods-burstable.slice/kubepods-burstable-podb8e19089_d5bc_4ed0_bc68_08cfb2074e0b.slice
53m         Warning   FailedCreatePodSandBox   pod/ovs-mrzbh   Failed create pod sandbox: rpc error: code = Unknown desc = cri-o configured with cgroupfs cgroup manager, but received systemd slice as parent: /kubepods.slice/kubepods-burstable.slice/kubepods-burstable-pode96bcbdc_8ef7_41ee_9988_b008169083c7.slice
<unknown>   Normal    Scheduled                pod/ovs-nscs9   Successfully assigned openshift-sdn/ovs-nscs9 to <worker-node-example.com>
64s         Warning   FailedCreatePodSandBox   pod/ovs-nscs9   Failed create pod sandbox: rpc error: code = Unknown desc = cri-o configured with cgroupfs cgroup manager, but received systemd slice as parent: /kubepods.slice/kubepods-burstable.slice/kubepods-burstable-pod76448823_f60e_4a13_a9a9_f675b257e4c4.slice