Description of problem: When creating a pod with the kata admission controller running, the pod is failed to be created. Version-Release number of selected component (if applicable): NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.7.0-0.nightly-2021-02-13-071408 True False 16h Cluster version is 4.7.0-0.nightly-2021-02-13-071408 How reproducible: Occasionally Steps to Reproduce: 1. Make sure the admission controller is running 2. $oc new-app httpd 3. $oc get pods 4. $oc describe pod/<httpd_pod_name> Actual results: "Warning FailedCreatePodSandBox 18s (x12 over 3m38s) kubelet Failed to create pod sandbox: rpc error: code = Unknown desc = CreateContainer failed: Failed to check if grpc server is working: context deadline exceeded: unknown" Expected results: The pod should be running successfully Additional info:
upstream PR: https://github.com/kata-containers/kata-containers/pull/1544 This issue should be fixed now for most environments, it's still may encountered in certain cases, if node machine has low virtualization performance. fix needs to be evaluated (should be included in upcoming release)
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.8.2 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2021:2438