-
Bug
-
Resolution: Unresolved
-
Major
-
4.14.z
-
Moderate
-
No
-
8
-
uShift Sprint 255, uShift Sprint 256, uShift Sprint 257, uShift Sprint 258, uShift Sprint 259, uShift Sprint 261, uShift Sprint 262
-
7
-
False
-
Description of problem:
After installing new rpm-ostree version, the pods are in CreateContainerError state.
Showing this error:
Warning Failed 15m (x3 over 16m) kubelet (combined from similar events): Error: failed to mount container k8s_<POD>-7685458cdf_xxxx_301a0d64-1993-45b9-a040-0a94e7fb6b5b_0(c75248228fe35a43c43b4875183d314d50d48165512659745dcf10fedb4d7f13): readlink /var/lib/containers/storage/overlay/l/KBKAXATHXY65BFU6TBGFTMOCWS: no such file or directory
Version-Release number of selected component (if applicable):
MicroShift 4.14.15
$ grep microshift installed-rpms
microshift-4.14.15-202402291214.p0.gbf42eae.assembly.4.14.15.el9.x86_64 Wed May 29 07:57:52 2024
How reproducible:
N/A
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
- workaround can be applied, after removing the image and the pod, new pod is scheduled and the image is re-pulled from the registry. This fixes the issue.
- is related to
-
-
- New
-
