Microshift is unable to start:

May 15 15:33:48 XXXX.test microshift[1942]: kubelet E0515 15:33:48.908910    1942 node_container_manager_linux.go:62] "Failed to create cgroup" err="unable to start unit \"kubepods.slice\" (properties [{Name:De
scription Value:\"libcontainer container kubepods.slice\"} {Name:Wants Value:[\"-.slice\"]} {Name:MemoryAccounting Value:true} {Name:CPUAccounting Value:true} {Name:IOAccounting Value:true} {Name:TasksAccounting
Value:true} {Name:DefaultDependencies Value:false}]): Timeout waiting for systemd to create kubepods.slice" cgroupName=["kubepods"]
May 15 15:33:48 XXXX.test microshift[1942]: kubelet E0515 15:33:48.908954    1942 kubelet.go:1583] "Failed to start ContainerManager" err="unable to start unit \"kubepods.slice\" (properties [{Name:Description
Value:\"libcontainer container kubepods.slice\"} {Name:Wants Value:[\"-.slice\"]} {Name:MemoryAccounting Value:true} {Name:CPUAccounting Value:true} {Name:IOAccounting Value:true} {Name:TasksAccounting Value:true
} {Name:DefaultDependencies Value:false}]): Timeout waiting for systemd to create kubepods.slice"
May 15 15:33:48 XXXX.test systemd[1]: microshift.service: Main process exited, code=exited, status=1/FAILURE
May 15 15:33:48 XXXX.test systemd[1]: microshift.service: Failed with result 'exit-code'.
May 15 15:33:48 XXXX.test systemd[1]: Failed to start MicroShift.
May 15 15:33:48 XXXX.test systemd[1]: microshift.service: Consumed 11.148s CPU time.
...
May 15 15:33:48 XXXX.test systemd[1]: Created slice libcontainer container kubepods.slice.

4.18.2

Always

1. N/A
2.
3.

The kubepods.slice timeout waiting for systemd to create it but systemd claims its creating just after the timeout message appears. Seems like a race condition even though i have no more evidence except the logs already shown

Microshift boots without issue

The system is an immutable bootc build of Red Hat Device Edge