cri-o: no such file or directory during container creation.

Description

I can have a working pod in k8s, delete it and recreate it and with zero changes to the pod.yaml, it fails to launch.

Describe the results you received: pod enters CreateContainerError

kubelet logs: Jan 16 11:19:33 zathras.emsl.pnl.gov kubelet[1754]: E0116 11:19:33.930641 1754 pod_workers.go:186] Error syncing pod 277ece5d-faf2-11e7-b013-d481d7de48ad (“test4_default(277ece5d-faf2-11e7-b013-d481d7de48ad)”), skipping: failed to “StartContainer” for “main” with CreateContainerError: “container create failed: container_linux.go:274: starting container process caused "process_linux.go:366: container init caused \"rootfs_linux.go:57: mounting \\\"/var/lib/kubelet/pods/277ece5d-faf2-11e7-b013-d481d7de48ad/etc-hosts\\\" to rootfs \\\"/var/lib/containers/storage/overlay/ea92f6ebb1abf41dd2b3583fc1dc85340c7ecb4fd4098e10790986d72edab9ee/merged\\\" at \\\"/var/lib/containers/storage/overlay/ea92f6ebb1abf41dd2b3583fc1dc85340c7ecb4fd4098e10790986d72edab9ee/merged/etc/hosts\\\" caused \\\"no such file or directory\\\"\""\n” ^C

Describe the results you expected: a working container.

Additional information you deem important (e.g. issue happens only occasionally):

Output of crio --version: crio version 1.9.0 k8s 1.9.0

obtained from: https://cbs.centos.org/repos/virt7-container-common-candidate/x86_64/os/Packages/

Additional environment details (AWS, VirtualBox, physical, etc.): this is on a bare metal laptop.