What happened:

We have a random pod having issues where its status is not available to K8s (Api server) and when we login to assigned node we can see it via docker ps in some cases. As of now the solution is we restart kubelet on the node where the pod is assigned

15m         Normal    Scheduled                  pod/catalog-server-5f5cfdffd9-7b8pw    Successfully assigned apps/catalog-server-5f5cfdffd9-7b8pw to node5
4s          Warning   FailedCreatePodContainer   pod/catalog-server-5f5cfdffd9-7b8pw    unable to ensure pod container exists: failed to create container for [kubepods burstable pod3b7a3b5d-7685-43cb-a0ab-5b0646ba07d7] : dbus: connection closed by user

Warning  FailedCreatePodContainer  4m40s (x4642 over 16h)  kubelet  unable to ensure pod container exists: failed to create container for [kubepods besteffort poda3e18933-f1c9-4c86-a752-e355e632ef1c] : dbus: connection closed by user

What you expected to happen:

This is not happening in our other cluster which have the same containers but older version of kubernetes ranging from 1.14 to 1.17 which were created using kubeadm.

How to reproduce it (as minimally and precisely as possible): NA

Anything else we need to know?:

Environment:

• Kubernetes version (use kubectl version): v1.19.7
• Cloud provider or hardware configuration:
• OS (e.g: cat /etc/os-release): CentOS Linux release 7.9.2009 (Core)
• Kernel (e.g. uname -a): 5.4.91-1.el7.elrepo.x86_64
• Install tools: kubespray ( 2.15.0)
• Network plugin and version (if this is a network-related bug): cilium
• Others: