Skip to content

[Failing Test][sig-node] InodeEviction [Slow] [Serial] when we run containers that should cause DiskPressure should eventually evict all of the correct pods #131923

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
Open
pacoxu opened this issue May 23, 2025 · 2 comments
Open

[Failing Test][sig-node] InodeEviction [Slow] [Serial] when we run containers that should cause DiskPressure should eventually evict all of the correct pods #131923

pacoxu opened this issue May 23, 2025 · 2 comments
Labels
kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/node Categorizes an issue or PR as relevant to SIG Node. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@pacoxu
Copy link
Member

pacoxu commented May 23, 2025 •
edited
Loading

Which jobs are failing?

E2eNode Suite: [It] [sig-node] InodeEviction [Slow] [Serial] [Disruptive] [Feature:Eviction] when we run containers that should cause DiskPressure should eventually evict all of the correct pods

Which tests are failing?

ci-crio-cgroupv2-node-e2e-eviction

Since when has it been failing?

Keeps failing since 05-16
Flake before

Image

Testgrid link

https://testgrid.k8s.io/sig-node-cri-o#ci-crio-cgroupv2-node-e2e-eviction

Reason for failure (if possible)

{ failed [FAILED] Timed out after 900.027s.
Expected
    <*errors.errorString | 0xc0008a0d40>: 
    NodeCondition: DiskPressure not encountered
    {
        s: "NodeCondition: DiskPressure not encountered",
    }
to be nil
In [It] at: k8s.io/kubernetes/test/e2e_node/eviction_test.go:608 @ 05/23/25 01:30:55.069
}

Anything else we need to know?

#130663 is about containerd failure on ImageGCNoEviction. (A fix is in containerd v2.0.5)

But this one is for CRI-O.

Relevant SIG(s)

/sig
@pacoxu pacoxu added the kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. label May 23, 2025
@k8s-ci-robot k8s-ci-robot added needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels May 23, 2025
@pacoxu pacoxu changed the title [Failing Test][It] [sig-node] InodeEviction [Slow] [Serial] [Disruptive] [Feature:Eviction] when we run containers that should cause DiskPressure should eventually evict all of the correct pods[Changes] [Failing Test][It] [sig-node] InodeEviction [Slow] [Serial] when we run containers that should cause DiskPressure should eventually evict all of the correct pods May 23, 2025
@pacoxu pacoxu changed the title [Failing Test][It] [sig-node] InodeEviction [Slow] [Serial] when we run containers that should cause DiskPressure should eventually evict all of the correct pods [Failing Test][sig-node] InodeEviction [Slow] [Serial] when we run containers that should cause DiskPressure should eventually evict all of the correct pods May 23, 2025
@kannon92
Copy link
Contributor

/sig node

@k8s-ci-robot k8s-ci-robot added sig/node Categorizes an issue or PR as relevant to SIG Node. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels May 23, 2025
@haircommander
Copy link
Contributor

/cc

/triage accepted
/priority important-soon

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels May 28, 2025
@haircommander haircommander moved this from Triage to Issues - To do in SIG Node CI/Test Board May 28, 2025
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. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/node Categorizes an issue or PR as relevant to SIG Node. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
SIG Node CI/Test Board
Status: Issues - To do
Milestone
No milestone
Development

No branches or pull requests
4 participants
@pacoxu @kannon92 @haircommander @k8s-ci-robot
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy