-
Notifications
You must be signed in to change notification settings - Fork 43k
Summary API [NodeConformance] test breaks on CRIO #95320
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.
Description
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:
While trying to run the node conformance tests with CRIO, the test
Summary API [NodeConformance]I noticed failures likeping: permission denied (are you root?)on the logs of the test containers. This happens because CRIO doesn't ship withCAP_NEW_RAWcapability enabled by default. Since only this test inNodeConformancerequires it, we should add this capability only in this test and not runtime wide.Which test(s) are failing:
Summary API [NodeConformance]Since when has it been failing:
Testgrid link:
Reason for failure:
CRIO doesn't ship with
CAP_NEW_RAWby default.Anything else we need to know: