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.

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

Fix scheduler extenders being not called on preemptions #103019

Merged

Conversation

ordovicia
Copy link
Contributor

@ordovicia ordovicia commented Jun 19, 2021

What type of PR is this?

/kind bug
/sig scheduling

What this PR does / why we need it:

This PR fixes a bug that scheduler extenders are not called on preemptions because frameworkImpl.extenders is not set.

Which issue(s) this PR fixes:

Fixes #102971

Special notes for your reviewer:

None

Does this PR introduce a user-facing change?

Fixed a regression in 1.20+ scheduler extender setup that scheduler extenders are not called on preemptions

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:


@k8s-ci-robot k8s-ci-robot added release-note Denotes a PR that will be considered when it comes time to generate release notes. kind/bug Categorizes issue or PR as related to a bug. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Jun 19, 2021
@k8s-ci-robot
Copy link
Contributor

Welcome @ordovicia!

It looks like this is your first PR to kubernetes/kubernetes 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/kubernetes has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

@k8s-ci-robot k8s-ci-robot added needs-priority Indicates a PR lacks a `priority/foo` label and requires one. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Jun 19, 2021
@k8s-ci-robot
Copy link
Contributor

Hi @ordovicia. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

@ahg-g
Copy link
Member

ahg-g commented Jun 19, 2021

/ok-to-test

@k8s-ci-robot k8s-ci-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Jun 19, 2021
@ahg-g
Copy link
Member

ahg-g commented Jun 20, 2021

/lgtm
/approve

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jun 20, 2021
@ahg-g
Copy link
Member

ahg-g commented Jun 20, 2021

Can you please create a cherry pick to 1.21 and 1.20 once this is merged?

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ahg-g, ordovicia

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 20, 2021
@k8s-ci-robot k8s-ci-robot merged commit dd213f0 into kubernetes:master Jun 20, 2021
@k8s-ci-robot k8s-ci-robot added this to the v1.22 milestone Jun 20, 2021
@ordovicia ordovicia deleted the fix-scheduler-framework-extenders branch June 21, 2021 02:18
@ordovicia
Copy link
Contributor Author

@ahg-g Thank you for your review. I have submitted cherry-pick PRs: #103030, #103031

@ahg-g
Copy link
Member

ahg-g commented Jun 21, 2021

Thanks, it would be great if you can add an integration test to https://github.com/kubernetes/kubernetes/blob/master/test/integration/scheduler/extender_test.go

@RyanBouchard
Copy link

@ordovicia I'm interested in adding this integration test, may I take it?

@ahg-g
Copy link
Member

ahg-g commented Jun 23, 2021

pls go ahead.

@RyanBouchard
Copy link

Thank you! I will start working on that.

RyanBouchard added a commit to RyanBouchard/kubernetes that referenced this pull request Jul 30, 2021
The unit test ensures extenders are being called during preemption
process as per changes in PR kubernetes#103019. To ensure extenders are being
called during preemption, had to add the following in
TestGenericSchedulerWithExtenders:

 - subtest to register defaultpreemption plugin as PostFilter
 - runtime.WithExteenders() to ensure extenders are passed in test

To register defaultpreemption plugin as PostFilter, had to define
RegisterPostFilterPlugin in pkg/scheduler/testing/framework_helpers.go

See also: kubernetes#103019
@cpanato
Copy link
Member

cpanato commented Aug 6, 2021

/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. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. labels Aug 6, 2021
k8s-ci-robot added a commit that referenced this pull request Aug 6, 2021
…03019-upstream-release-1.21

Automated cherry pick of #103019: Fix frameworkImpl.extenders being not set
k8s-ci-robot added a commit that referenced this pull request Aug 6, 2021
…03019-upstream-release-1.20

Automated cherry pick of #103019: Fix frameworkImpl.extenders being not set
@RyanBouchard
Copy link

@ordovicia @ahg-g I apologize for the long absence. I originally working on adding an integration test, then I discussed with Huang-Wei about covering this with a unit test instead; however, other things have since come up, and I don't think I will get to this in a reasonable amount of time. I closed my PR to avoid holding things up any further. I believe a test is still needed.

@liggitt liggitt added the kind/regression Categorizes issue or PR as related to a regression from a prior release. label Apr 27, 2022
@ordovicia ordovicia changed the title Fix scheduler extenders being not called on preemptions Fix scheduler extenders being not called on preemption Oct 26, 2023
@ordovicia ordovicia changed the title Fix scheduler extenders being not called on preemption Fix scheduler extenders being not called on preemptions Oct 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/bug Categorizes issue or PR as related to a bug. kind/regression Categorizes issue or PR as related to a regression from a prior release. lgtm "Looks good to me", indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. release-note Denotes a PR that will be considered when it comes time to generate release notes. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

scheduler: frameworkImpl.extenders is not set
6 participants