What happened?

1 static pod kube-controller-manager shows one container is not running, but indicates the cluster-policy-controller container is not running
2 But we found the cluster-policy-controller is in running state, but use crictl ps -a | grep cluster-policy-controller , we found there still one exited state container with the same name cluster-policy-controller
3 After deleteing the exited state cluster-policy-controller, the static pods run normally

What did you expect to happen?

The exited container should not impact the running container

How can we reproduce it (as minimally and precisely as possible)?

just see this 2-3 times, have no idea how to reproduce

Anything else we need to know?

Sep 28 22:29:49 ceacube-node-1 crio[2687]: time="2024-09-28 22:29:49.788387251+08:00" level=info msg="Creating container: kube-controller-manager/kube-controller-manager-ceacube-node-1/cluster-policy-controller" id=b5a2b26e-8839-499e-b0e1-08a79e876c5a name=/runtime.v1.RuntimeService/CreateContainer
Sep 28 22:29:50 ceacube-node-1 crio[2687]: time="2024-09-28 22:29:50.063205936+08:00" level=info msg="Created container 7bf4275d70ac589d3b3a47079ce5381a50550576069d69b25f4f6c79fd14f27e: kube-controller-manager/kube-controller-manager-ceacube-node-1/cluster-policy-controller" id=b5a2b26e-8839-499e-b0e1-08a79e876c5a name=/runtime.v1.RuntimeService/CreateContainer
Sep 28 22:29:50 ceacube-node-1 crio[2687]: time="2024-09-28 22:29:50.070217817+08:00" level=info msg="Started container" PID=5646 containerID=7bf4275d70ac589d3b3a47079ce5381a50550576069d69b25f4f6c79fd14f27e description=kube-controller-manager/kube-controller-manager-ceacube-node-1/cluster-policy-controller id=0d17149a-906d-4ac0-9cfa-1a08497f8ea4 name=/runtime.v1.RuntimeService/StartContainer sandboxID=392c8ec60512021d082951323ceb2af466e1e563960c84f11da07575aae413a2
Sep 28 22:30:09 ceacube-node-1 crio[2687]: time="2024-09-28 22:30:09.676336926+08:00" level=info msg="Creating container: kube-controller-manager/kube-controller-manager-ceacube-node-1/cluster-policy-controller" id=31fbba8c-7ca9-4384-8650-224cfe11e69d name=/runtime.v1.RuntimeService/CreateContainer
Sep 28 22:30:09 ceacube-node-1 crio[2687]: time="2024-09-28 22:30:09.676440556+08:00" level=warning msg="error reserving ctr name k8s_cluster-policy-controller_kube-controller-manager-ceacube-node-1_kube-controller-manager_900d399cfd7e9b99ab28cfda48d2aea1_7 for id 2851fd3c0993b4c6bc59abf6c5b1236217860581ae94946674726364f117bc17: name is reserved"
Sep 28 22:32:34 ceacube-node-1 crio[2687]: time="2024-09-28 22:32:34.967170577+08:00" level=info msg="Creating container: kube-controller-manager/kube-controller-manager-ceacube-node-1/cluster-policy-controller" id=9527cf77-27fb-4cce-80d1-1d317b9492ac name=/runtime.v1.RuntimeService/CreateContainer
Sep 28 22:32:35 ceacube-node-1 crio[2687]: time="2024-09-28 22:32:35.066026617+08:00" level=info msg="Created container 535dbf8b8e9d42c8807ddb8656439d661227dfa9b5814d6a8e87dbe8852e48d2: kube-controller-manager/kube-controller-manager-ceacube-node-1/cluster-policy-controller" id=9527cf77-27fb-4cce-80d1-1d317b9492ac name=/runtime.v1.RuntimeService/CreateContainer
Sep 28 22:32:35 ceacube-node-1 crio[2687]: time="2024-09-28 22:32:35.072205289+08:00" level=info msg="Started container" PID=3283 containerID=535dbf8b8e9d42c8807ddb8656439d661227dfa9b5814d6a8e87dbe8852e48d2 description=kube-controller-manager/kube-controller-manager-ceacube-node-1/cluster-policy-controller id=5bc3a429-19e6-473f-816f-defd1ee563c0 name=/runtime.v1.RuntimeService/StartContainer sandboxID=392c8ec60512021d082951323ceb2af466e1e563960c84f11da07575aae413a2

Sep 28 22:36:48 ceacube-node-1 crio[2687]: time="2024-09-28 22:36:48.963159617+08:00" level=info msg="Creating container: kube-controller-manager/kube-controller-manager-ceacube-node-1/cluster-policy-controller" id=99b1e91b-9c2c-4351-9830-d9839a9993ce name=/runtime.v1.RuntimeService/CreateContainer
Sep 28 22:36:48 ceacube-node-1 crio[2687]: time="2024-09-28 22:36:48.963274377+08:00" level=warning msg="error reserving ctr name k8s_cluster-policy-controller_kube-controller-manager-ceacube-node-1_kube-controller-manager_900d399cfd7e9b99ab28cfda48d2aea1_7 for id 4adb888a9e9630f59d35d5a076ace090eab96ec9e546182b162911007cc7bb1e: name is reserved"

CRI-O and Kubernetes version

$ crio --version
# paste output here
1.25.8

$ kubectl version --output=json
# paste output here

OS version

# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
5.15.131-8
# paste output here

Additional environment details (AWS, VirtualBox, physical, etc.)