-
Notifications
You must be signed in to change notification settings - Fork 1.2k
[Cherry-pick 1.13] Fix scheduler panic by moving InitKubeSchedulerRelatedMetrics outside… #4735
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
Conversation
… conditional Co-authored-by: JesseStutler <38534065+JesseStutler@users.noreply.github.com>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Summary of ChangesHello @JesseStutler, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request addresses a critical bug where the Kubernetes scheduler would panic due to a nil pointer dereference if started with metrics disabled. The fix ensures that a crucial metrics initialization function, which is unconditionally accessed by scheduler framework plugins, is always called regardless of whether metrics or pprof are explicitly enabled, thereby stabilizing the scheduler's startup process. Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
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.
Code Review
This pull request addresses a critical bug that causes the scheduler to panic when started without metrics enabled. The fix involves moving the initialization of Kubernetes scheduler-related metrics to be unconditional, which correctly prevents the nil pointer dereference. The change is simple, effective, and includes a clear comment explaining why the initialization is always necessary. The fix is well-implemented and resolves the issue as described.
|
/close Merged with #4770 |
|
@hajnalmt: Closed this PR. DetailsIn 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/test-infra repository. |
Cherry-picks #4731 for
release-1.13.What type of PR is this?
Bug fix
What this PR does / why we need it:
Scheduler panics with nil pointer dereference during pod scheduling when started without
--enable-metrics=true. The Kubernetes scheduler framework plugins unconditionally accessk8smetrics.Goroutines, which was only initialized when metrics were enabled.Changes:
metrics.InitKubeSchedulerRelatedMetrics()outside theif opt.EnableMetrics || opt.EnablePprofblock incmd/scheduler/app/server.gok8smetrics.Goroutinesis always initialized before scheduler startsWhich issue(s) this PR fixes:
Fixes #4729
Does this PR introduce a user-facing change?