-
Notifications
You must be signed in to change notification settings - Fork 42k
Open
Labels
kind/flakeCategorizes issue or PR as related to a flaky test.Categorizes issue or PR as related to a flaky test.priority/backlogHigher priority than priority/awaiting-more-evidence.Higher priority than priority/awaiting-more-evidence.priority/important-longtermImportant over the long term, but may not be staffed and/or may need multiple releases to complete.Important over the long term, but may not be staffed and/or may need multiple releases to complete.sig/nodeCategorizes an issue or PR as relevant to SIG Node.Categorizes an issue or PR as relevant to SIG Node.triage/acceptedIndicates an issue or PR is ready to be actively worked on.Indicates an issue or PR is ready to be actively worked on.
Description
Which jobs are flaking?
- ci-kubernetes-node-swap-fedora-serial
Which tests are flaking?
- E2eNode Suite.[It] [sig-node] Device Plugin [NodeFeature:DevicePlugin] [Serial] DevicePlugin [Serial] [Disruptive] Keeps device plugin assignments after kubelet restart and device plugin restart (no pod restart)
Since when has it been flaking?
#121220 is an old issue which include this flake there last year.
/cc @kannon92
Testgrid link
https://testgrid.k8s.io/sig-node-kubelet#kubelet-gce-e2e-swap-fedora-serial
Reason for failure (if possible)
{ failed [FAILED] inconsistent device assignment after pod restart: no resources found for device-plugin-errors-3704/device-plugin-test-4a0b7496-f40b-43f8-a726-d2d3a6ab3bcb/device-plugin-test-4a0b7496-f40b-43f8-a726-d2d3a6ab3bcb
In [It] at: k8s.io/kubernetes/test/e2e_node/device_plugin_test.go:613 @ 10/15/24 15:50:21.431
}
Anything else we need to know?
No response
Relevant SIG(s)
/sig node
Metadata
Metadata
Assignees
Labels
kind/flakeCategorizes issue or PR as related to a flaky test.Categorizes issue or PR as related to a flaky test.priority/backlogHigher priority than priority/awaiting-more-evidence.Higher priority than priority/awaiting-more-evidence.priority/important-longtermImportant over the long term, but may not be staffed and/or may need multiple releases to complete.Important over the long term, but may not be staffed and/or may need multiple releases to complete.sig/nodeCategorizes an issue or PR as relevant to SIG Node.Categorizes an issue or PR as relevant to SIG Node.triage/acceptedIndicates an issue or PR is ready to be actively worked on.Indicates an issue or PR is ready to be actively worked on.
Type
Projects
Status
Issues - In progress