-
Notifications
You must be signed in to change notification settings - Fork 41.1k
always pull pause image for eviction tests #133349
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
always pull pause image for eviction tests #133349
Conversation
/test |
@kannon92: The
The following commands are available to trigger optional jobs:
Use
In response to this:
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. |
/sig node /test pull-crio-cgroupv2-node-e2e-eviction |
f8dd567
to
e83e581
Compare
/test pull-crio-cgroupv2-node-e2e-eviction |
This seems to fix the problem. There are other failures in eviction that we have not yet solved. But at least this solves the other failures related to pause. |
Name: podName, | ||
Image: imageutils.GetPauseImageName(), | ||
Name: podName, | ||
ImagePullPolicy: "Always", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Always seems a bit aggressive. I would expect IfNotPresent
will work
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking at other images in eviction, they were using Always. If you want this, can we do this as one fix rather than one-offs?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here is the follow up. #133359
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve
/milestone v1.34
this is test-only low risk change and causing test failures
/hold
I am fine with Always, but it may be cheaper to change to IfNotPresent. Holding for this
LGTM label has been added. Git tree hash: a995189fb59311c9d4f71da935f3e7e087ca86b2
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kannon92, SergeyKanzhelev The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/hold cancel I would like to make a change like this once and see the impact. I don't think this should block this PR. |
@kannon92: 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. 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. I understand the commands that are listed here. |
The Kubernetes project has merge-blocking tests that are currently too flaky to consistently pass. This bot retests PRs for certain kubernetes repos according to the following rules:
You can:
/retest |
What type of PR is this?
/kind failing-test
What this PR does / why we need it:
Which issue(s) this PR is related to:
Fixes #133348
Special notes for your reviewer:
See the issue for RCA.
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: