Skip to content

"OCI runtime start failed" runc race causes many CI failures/flakes #86312

@liggitt

Description

@liggitt

Which jobs are flaking:
pull-kubernetes-e2e-gce
ci-cos-containerd-e2e-ubuntu-gce
ci-kubernetes-e2e-kops-gce

Changes needed to get the fix into official containerd releases:

As I understand it, this is what we need to get the fix into our CI environments:

For kind:

For GCE / kube-up:

Which test(s) are flaking:

  • [sig-storage] ConfigMap should be consumable from pods in volume as non-root with FSGroup [LinuxOnly] [NodeFeature:FSGroup]
  • [sig-storage] Projected downwardAPI should provide podname as non-root with fsgroup [LinuxOnly] [NodeFeature:FSGroup]
  • [sig-storage] Projected configMap should be consumable from pods in volume with mappings as non-root [NodeConformance] [Conformance]
  • [sig-storage] EmptyDir volumes should support (root,0644,tmpfs) [LinuxOnly] [NodeConformance] [Conformance]
  • [sig-storage] In-tree Volumes [Driver: hostPathSymlink] [Testpattern: Inline-volume (default fs)] subPath should support file as subpath [LinuxOnly]
  • [sig-storage] In-tree Volumes [Driver: local][LocalVolumeType: blockfs] [Testpattern: Pre-provisioned PV (default fs)] subPath should support readOnly file specified in the volumeMount [LinuxOnly]

Testgrid link:

Reason for failure:

runc race condition fixed in opencontainers/runc#2185

Anything else we need to know:
https://storage.googleapis.com/k8s-gubernator/triage/index.html?text=OCI%20runtime%20start%20failed

Test containers appear to be exiting with a CRI error?

/sig node
for CRI expertise

/sig storage
for test ownership

Metadata

Metadata

Labels

kind/bugCategorizes issue or PR as related to a bug.kind/failing-testCategorizes issue or PR as related to a consistently or frequently failing test.lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.priority/critical-urgentHighest priority. Must be actively worked on as someone's top priority right now.sig/nodeCategorizes an issue or PR as relevant to SIG Node.sig/storageCategorizes an issue or PR as relevant to SIG Storage.

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions