-
Notifications
You must be signed in to change notification settings - Fork 39.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cos-cgroupv2-containerd-node-e2e-serial failing after feature gate was GA'd #114475
Comments
@bobbypage: This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/sig node |
We likely need to remove all references of the feature gate: i.e. https://sourcegraph.com/search?q=context:global+repo:%5Egithub%5C.com/kubernetes/test-infra%24+file:%5Econfig/jobs/kubernetes/sig-node+LocalStorageCapacityIsolation&patternType=standard&sm=1 |
The following tests are also failing due to the missing feature gate flag: |
yeah, same here #114449 |
What happened?
cos-cgroupv2-containerd-node-e2e-serial is failing. https://testgrid.k8s.io/sig-node-containerd#cos-cgroupv2-containerd-node-e2e-serial
Example: https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-cos-cgroupv2-containerd-node-e2e-serial/1602401700964995072
This is appears due to #114410 which removed the
LocalStorageCapacityIsolation
feature gate after it was GA'dWe should probably update the test-infra config to avoid setting this feature gate now since it is GA.
What did you expect to happen?
n/a
How can we reproduce it (as minimally and precisely as possible)?
n/a
Anything else we need to know?
n/a
Kubernetes version
Cloud provider
OS version
Install tools
Container runtime (CRI) and version (if applicable)
Related plugins (CNI, CSI, ...) and versions (if applicable)
/help
The text was updated successfully, but these errors were encountered: