-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Labels
kind/failing-testCategorizes issue or PR as related to a consistently or frequently failing test.Categorizes issue or PR as related to a consistently or frequently failing test.
Description
Which jobs are failing?
- fedora-integration
- fedora-kata
- cgroupv2-integration
Which tests are failing?
OCI image volume mount lifecycle
Examples:
- https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/cri-o_cri-o/8403/pull-ci-cri-o-cri-o-main-ci-cgroupv2-integration/1814667518363570176
- https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/cri-o_cri-o/8403/pull-ci-cri-o-cri-o-main-ci-fedora-integration/1814667518401318912
Since when has it been failing?
First seen on July 19th, which is the day where the test was introduced (with #8317)
Testgrid link
No response
Reason for failure (if possible)
not ok 233 OCI image volume mount lifecycle
# (in test file ./oci_volumes.bats, line 33)
# `CTR_ID=$(crictl run "$TESTDIR/container.json" "$TESTDATA/sandbox_config.json")' failed
# time="2024-07-20 14:48:49.085772566Z" level=info msg="Starting CRI-O, version: 1.31.0, git: 6e9ef2600d26a6510439a8f2898569035b7b8fe0(dirty)"
# level=info msg="Using default capabilities: CAP_CHOWN, CAP_DAC_OVERRIDE, CAP_FSETID, CAP_FOWNER, CAP_SETGID, CAP_SETUID, CAP_SETPCAP, CAP_NET_BIND_SERVICE, CAP_KILL"
# time="2024-07-20 14:48:49.175521404Z" level=info msg="Starting CRI-O, version: 1.31.0, git: 6e9ef2600d26a6510439a8f2898569035b7b8fe0(dirty)"
# level=info msg="Using default capabilities: CAP_CHOWN, CAP_DAC_OVERRIDE, CAP_FSETID, CAP_FOWNER, CAP_SETGID, CAP_SETUID, CAP_SETPCAP, CAP_NET_BIND_SERVICE, CAP_KILL"
# time="2024-07-20T14:48:49Z" level=fatal msg="validate service connection: validate CRI v1 runtime API for endpoint \"unix:///tmp/tmp.i2JoJF2mmu/crio.sock\": rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing: dial unix /tmp/tmp.i2JoJF2mmu/crio.sock: connect: no such file or directory\""
# Image is up to date for quay.io/crio/artifact@sha256:52c997d8906f39c5b5550dd1f05fd785fb46bbb50eb055f9df61df6dc9e3a6cd
# E0720 14:48:51.982098 90092 remote_runtime.go:319] "CreateContainer in sandbox from runtime service failed" err="rpc error: code = Unknown desc = mount.HostPath is empty" podSandboxID="05287d8aee1568395499880cec3242c97c47b6500815d834c931f714d63cbad9"
# time="2024-07-20T14:48:51Z" level=fatal msg="running container: creating container failed: rpc error: code = Unknown desc = mount.HostPath is empty"
Anything else we need to know?
No response
Metadata
Metadata
Assignees
Labels
kind/failing-testCategorizes issue or PR as related to a consistently or frequently failing test.Categorizes issue or PR as related to a consistently or frequently failing test.