-
Notifications
You must be signed in to change notification settings - Fork 39.4k
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
Skip updating scheduler cache on pod update if the node was deleted #89908
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: alculquicondor 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 |
/assign @ahg-g |
7447978
to
83565af
Compare
/retest |
83565af
to
acd2933
Compare
/priority critical-urgent |
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.
tests are failing
if err := cache.removePod(oldPod); err != nil { | ||
return err | ||
} | ||
cache.addPod(newPod) |
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.
Yeah, this was the mistake
Signed-off-by: Aldo Culquicondor <acondor@google.com>
acd2933
to
e75b5dc
Compare
/lgtm |
/retest |
@alculquicondor: 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/test-infra repository. I understand the commands that are listed here. |
/retest Review the full test history for this PR. Silence the bot with an |
we should backport this, right? |
Yes, I'm on it. |
…f-#89908-upstream-release-1.18 Automated cherry pick of #89908: Skip updating cache on pod update if the node was deleted
… update if the node was deleted Signed-off-by: PingWang <wang.ping5@zte.com.cn>
What type of PR is this?
/kind bug
What this PR does / why we need it:
/sig scheduling
Skip updating scheduler cache on pod update if the node was deleted. This can happen when events arrive out of order.
The fix doesn't skip updates on pods that might arrive before its node is created. There will always be a pod creation event first that would cause the cache to add a placeholder node.
Add unit test for out-of-order pod/node creation/removal.
This should help spot bugs when:
Which issue(s) this PR fixes:
Fixes #89552
This only reproduced with at least 2 pods in the node being removed.
Does this PR introduce a user-facing change?: