-
Notifications
You must be signed in to change notification settings - Fork 43k
Capability set incorrectly. CAP_NET_RAW should be NET_RAW. #95612
Copy link
Copy link
Closed
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.needs-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.Indicates an issue or PR lacks a `triage/foo` label and requires one.sig/nodeCategorizes an issue or PR as relevant to SIG Node.Categorizes an issue or PR as relevant to SIG Node.
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.needs-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.Indicates an issue or PR lacks a `triage/foo` label and requires one.sig/nodeCategorizes an issue or PR as relevant to SIG Node.Categorizes an issue or PR as relevant to SIG Node.
Which jobs are failing:
ci-cri-containerd-node-e2e
Which test(s) are failing:
Summary API [NodeConformance] when querying /stats/summary should report resource usage through the stats api
Since when has it been failing:
2020 10-12 09:04 PDT
Since #95321
Testgrid link:
https://testgrid.k8s.io/sig-node-containerd#node-e2e
Reason for failure:
Capability set incorrectly. CAP_NET_RAW should be NET_RAW.
I1013 18:39:19.058] Oct 13 18:10:51.403: INFO: At 2020-10-13 18:09:34 +0000 UTC - event for stats-busybox-0: {kubelet tmp-node-e2e-033aeade-cos-81-12871-1210-0} Failed: Error: failed to create containerd task: OCI runtime create failed: container_linux.go:370: starting container process caused: unknown capability "CAP_CAP_NET_RAW": unknown
Anything else we need to know:
I have no idea where this is documented. It's a best guess.