Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[Failing Test] when we run containers that should cause use quotas for LSCI monitoring should eventually evict all of the correct pods #128042

Closed
pacoxu opened this issue Oct 14, 2024 · 1 comment · Fixed by #128074
Closed

[Failing Test] when we run containers that should cause use quotas for LSCI monitoring should eventually evict all of the correct pods #128042

pacoxu opened this issue Oct 14, 2024 · 1 comment · Fixed by #128074
Labels
kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. sig/node Categorizes an issue or PR as relevant to SIG Node.

Comments

@pacoxu
Copy link
Member

pacoxu commented Oct 14, 2024

Which jobs are failing?

  • pull-kubernetes-node-crio-cgrpv2-userns-e2e-serial

Which tests are failing?

E2eNode Suite: [It] [sig-node] LocalStorageCapacityIsolationFSQuotaMonitoring [Slow] [Serial] [Disruptive] [Feature:LocalStorageCapacityIsolationQuota] [NodeFeature:LSCIQuotaMonitoring] [NodeFeature:UserNamespacesSupport] [Feature:UserNamespacesSupport] when we run containers that should cause use quotas for LSCI monitoring (quotas enabled: true) should eventually evict all of the correct pods

Since when has it been failing?

Since added in kubernetes/test-infra#33511

Testgrid link

https://prow.k8s.io/job-history/gs/kubernetes-jenkins/pr-logs/directory/pull-kubernetes-node-crio-cgrpv2-userns-e2e-serial

Reason for failure (if possible)


Run #0: Skipped expand_less5s<nil>  Run #0: Skipped expand_less  5s

Run #0: Skipped expand_less 
<nil>
Run #1: Failed expand_less11m57s{ failed [FAILED] Timed out after 600.001s. Expected success, but got an error:     <*errors.errorString \| 0xc00191dbb0>:      pods that should be evicted are still running: []string{"emptydir-concealed-disk-over-sizelimit-quotas-true-pod"}     {         
s: "pods that should be evicted are still running: []string{\"emptydir-concealed-disk-over-sizelimit-quotas-true-pod\"}",    
 } In [It] at: k8s.io/kubernetes/test/e2e_node/eviction_test.go:649 @ 09/27/24 12:25:08.707 } | Run #1: Failed expand_less | 11m57s | { failed [FAILED] Timed out after 600.001s. Expected success, but got an error:   
  <*errors.errorString \| 0xc00191dbb0>:   
   pods that should be evicted are still running: []string{"emptydir-concealed-disk-over-sizelimit-quotas-true-pod"}     {        
 s: "pods that should be evicted are still running: []string{\"emptydir-concealed-disk-over-sizelimit-quotas-true-pod\"}",    
 } In [It] at: k8s.io/kubernetes/test/e2e_node/eviction_test.go:649 @ 09/27/24 12:25:08.707 }
Run #1: Failed expand_less  
{ failed [FAILED] Timed out after 600.001s. Expected success, but got an error:  
   <*errors.errorString \| 0xc00191dbb0>:      pods that should be evicted are still running: []string{"emptydir-concealed-disk-over-sizelimit-quotas-true-pod"}     {       
  s: "pods that should be evicted are still running: []string{\"emptydir-concealed-disk-over-sizelimit-quotas-true-pod\"}",  
   } In [It] at: k8s.io/kubernetes/test/e2e_node/eviction_test.go:649 @ 09/27/24 12:25:08.707 }

Anything else we need to know?

This is related to kubernetes/enhancements#1029.

Relevant SIG(s)

/sig node
@pacoxu pacoxu added the kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. label Oct 14, 2024
@k8s-ci-robot k8s-ci-robot added the sig/node Categorizes an issue or PR as relevant to SIG Node. label Oct 14, 2024
@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Oct 14, 2024
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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-sigs/prow repository.

@pacoxu pacoxu changed the title [Failing Test] when we run containers that should cause use quotas for LSCI monitoring (quotas enabled: true) should eventually evict all of the correct pods [Failing Test] when we run containers that should cause use quotas for LSCI monitoring should eventually evict all of the correct pods Oct 14, 2024
This was referenced Oct 14, 2024
Open
Closed
Merged
@github-project-automation github-project-automation bot moved this from Triage to Done in SIG Node CI/Test Board Oct 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. sig/node Categorizes an issue or PR as relevant to SIG Node.
Projects
SIG Node CI/Test Board
Status: Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

storage fsquota monitoring pod should be user namespaced pacoxu/kubernetes
2 participants
@pacoxu @k8s-ci-robot