Extend E2E test coverage for PSI metrics under pressure#132824
Extend E2E test coverage for PSI metrics under pressure#132824k8s-ci-robot merged 2 commits intokubernetes:masterfrom
Conversation
|
Skipping CI for Draft Pull Request. |
|
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 DetailsInstructions 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. |
|
/assign |
10f6011 to
7f76c95
Compare
73f9edd to
a55f1ea
Compare
a55f1ea to
6c156db
Compare
|
It took me a long time to realize that the error is only happening to the ubuntu tests, but not COS :( From the naming, it looks like we are using cgroup v1 with Ubuntu in our tests... |
|
In comparison, previously we were using "non cgroup v1" ubuntu images when the tests passed |
|
The test log suggests the image is from |
f385b4e to
252513a
Compare
|
/test pull-kubernetes-node-e2e-containerd-kubelet-psi |
|
Since we don't have control over what's behind Open comments are addressed and the test has passed. This PR is ready for review. Filed a test-infra issue kubernetes/test-infra#35211 |
|
Integration test failure unrelated |
|
LGTM label has been added. DetailsGit tree hash: afc079b6c263acf77aa689d728f65c1ee194709d |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: roycaihw, SergeyKanzhelev The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest |
|
/milestone v1.34 |
|
/test pull-kubernetes-e2e-gce |
|
@roycaihw: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. DetailsInstructions 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. I understand the commands that are listed here. |
|
I'll trigger the retest after the revert is merged: #133203 |
|
/retest |
What type of PR is this?
/kind feature
What this PR does / why we need it:
Validate that PSI metrics are correctly reported under various resource pressure scenarios.
Which issue(s) this PR is related to:
Ref: #132822
Does this PR introduce a user-facing change?
/sig node
/priority important-soon