cri-o couldn't restore sandbox after restart #5569
Description
Description
Steps to reproduce the issue:
systemctl restart crio
Describe the results you received:
time="2022-01-25 22:39:47.503233946+08:00" level=warning msg="Could not restore sandbox cea6108e468e07608b4c1fec5c4d3938afdda9976a33f6d0c6fa2e258cb8c1c0: error reading sandbox state from disk \"cea6108e468e07608b4c1fec5c4d3938afdda9976a33f6d0c6fa2e258cb8c1c0\": runtime not correctly setup"
time="2022-01-25 22:39:47.528077413+08:00" level=warning msg="Unable to delete container k8s_POD_zhaoyangsun-sun-3_tispace_f86ce375-c518-4d61-a1e4-b10474ca42c0_0: 1 error occurred:\n\t* unlinkat /run/containers/storage/overlay-containers/cea6108e468e07608b4c1fec5c4d3938afdda9976a33f6d0c6fa2e258cb8c1c0/userdata/shm: device or resource busy\n\n"
time="2022-01-25 22:39:47.530670190+08:00" level=warning msg="Deleting all containers under sandbox cea6108e468e07608b4c1fec5c4d3938afdda9976a33f6d0c6fa2e258cb8c1c0 since it could not be restored"
time="2022-01-25 22:39:47.609206032+08:00" level=warning msg="Could not restore sandbox 2e03d4118a732606985bc702386dbb5946822f00cd8b0675f500559f12a593cc: error reading sandbox state from disk \"2e03d4118a732606985bc702386dbb5946822f00cd8b0675f500559f12a593cc\": runtime not correctly setup"
time="2022-01-25 22:39:47.630005492+08:00" level=warning msg="Unable to delete container k8s_POD_xiayujie-dev01_tispace_86c66f39-2346-451f-b002-998d4a6e8ce7_0: 1 error occurred:\n\t* unlinkat /run/containers/storage/overlay-containers/2e03d4118a732606985bc702386dbb5946822f00cd8b0675f500559f12a593cc/userdata/shm: device or resource busy\n\n"
time="2022-01-25 22:39:47.632355087+08:00" level=warning msg="Deleting all containers under sandbox 2e03d4118a732606985bc702386dbb5946822f00cd8b0675f500559f12a593cc since it could not be restored"
Then crio created a new sandbox and the old sandbox was leak.
Describe the results you expected:
crio could restore the existing sandbox.
Additional information you deem important (e.g. issue happens only occasionally):
runtime is kata
[crio.runtime.runtimes.kata]
runtime_path = "/opt/kata/bin/containerd-shim-kata-v2"
runtime_type = "vm"
runtime_root = "/run/vc"
privileged_without_host_devices = true
Output of crio --version:
crio version 1.22.1
Version: 1.22.1
GitCommit: 63ca93845d5fe05cdca826367afcb601ece8d7ad
GitTreeState: clean
BuildDate: 2021-12-03T20:37:36Z
GoVersion: go1.16.8
Compiler: gc
Platform: linux/amd64
Linkmode: dynamic
BuildTags: exclude_graphdriver_devicemapper, seccomp
SeccompEnabled: true
AppArmorEnabled: false
Additional environment details (AWS, VirtualBox, physical, etc.):