Bug 1710124 - [CRI-O] error creating read-write layer with ID no such file or directory
Summary: [CRI-O] error creating read-write layer with ID no such file or directory
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Node
Version: 3.11.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 3.11.z
Assignee: Peter Hunt
QA Contact: weiwei jiang
URL:
Whiteboard:
Depends On:
Blocks: 1186913
TreeView+ depends on / blocked
 
Reported: 2019-05-14 23:05 UTC by Steven Walter
Modified: 2023-09-07 20:01 UTC (History)
17 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-13 20:35:34 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Steven Walter 2019-05-14 23:05:57 UTC 
Description of problem:

Customer notes sometimes when application teams try to schedule their pods they see:
Failed create pod sandbox: rpc error: code = Unknown desc = error creating pod sandbox with name "k8s_test-exxample-15-xwsdw_example--example_3610-11e9-afa1-001a4a195f6a_0": error creating read-write layer with ID "23f96769bbe5xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxfa2ff4a7b3e7e": symlink ../23f96769bbe58288bae1bc6641bced0e55881dc0bd04046e15cfa2ff4a7b3e7e/diff /var/lib/containers/storage/overlay/l/4M53TMQASZFSDKR7R65KP4U4DF: no such file or directory"

Version-Release number of selected component (if applicable):
3.11

Working on getting crio and node logs
Comment 2 Mrunal Patel 2019-05-15 00:19:56 UTC 
The fix for this went into cri-o 1.11.14.
Comment 13 Urvashi Mohnani 2019-06-06 13:08:06 UTC 
Hi, could we get the cri-o logs or access to the cluster?
Comment 16 Urvashi Mohnani 2019-06-11 19:24:36 UTC 
The original issue where the symlinks were not found has been fixed. But looks like another issue is occurring now. I will need access to the cluster where this is happening to further debug what is going wrong.
Note You need to log in before you can comment on or make changes to this bug.