-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
4.18.z
-
None
-
None
-
False
-
-
0
-
Critical
-
None
-
None
-
None
-
None
-
uShift Sprint 284
-
1
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
When running iso installs and ostree z or y upgrades i see microshift pods goes into createContainerError state and doing a describe on the pods shows error below
openshift-ovn-kubernetes 3h20m Warning Failed pod/ovnkube-node-gscpl (combined from similar events): Error: container create failed: systemd failed to install eBPF device filter on cgroup `/sys/fs/cgroup/kubepods.slice/kubepods-burstable.slice/kubepods-burstable-poda2535c48_e30b_4620_93c2_afc19d1685c1.slice/crio-34e6ac00324e13e50481a795f54b5a1ace01bf2e8c186a75b407700d0ca66e5b.scope`
Version-Release number of selected component (if applicable):
4.18.33
microshift-4.18.33-202602090801.p0.ge2f5f13.assembly.4.18.33.el9.x86_64
How reproducible:
always
Steps to Reproduce:
1. Trigger iso installs and ostree z and y upgrades with microshift release testing pipeline.
2.
3.
Actual results:
Microshift pods fails to start with error as described in the description
Expected results:
Microshift pods should start fine.
Additional info:
https://redhat-internal.slack.com/archives/C03CJTNLKAT/p1770818291495579
- is caused by
-
OCPBUGS-66249 OCP 4.19.19: GPU workloads with readOnlyRootFilesystem=true fail to run, show NVIDIA hook errors
-
- Closed
-
- links to