Skip to content

panic install if labeled nodes are not found #5504

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

Merged
merged 1 commit into from
Jul 22, 2025
Merged

Conversation

oilbeater
Copy link
Collaborator

Pull Request

What type of this PR

Examples of user facing changes:

  • Bug fixes

Which issue(s) this PR fixes

Fixes #(issue-number)

@dosubot dosubot bot added the size:XS This PR changes 0-9 lines, ignoring generated files. label Jul 22, 2025
Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Summary of Changes

Hello @oilbeater, 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 significantly improves the reliability of the Kube-OVN installation process by introducing a pre-flight validation. It prevents silent failures or misconfigurations by ensuring that the required master nodes, identified by their labels, are present before proceeding with the deployment, thus providing immediate feedback to the user if a prerequisite is not met.

Highlights

  • Installation Robustness: I've added a critical check within the Helm helper templates (_helpers.tpl) for both kube-ovn and kube-ovn-v2 charts. This check ensures that if no nodes are found with the MASTER_NODES_LABEL during installation, the Helm deployment will now explicitly fail with a descriptive error message.
  • Improved Error Messaging: The new failure message clearly indicates that no nodes were found with the specified label and advises the user to verify their MASTER_NODES_LABEL configuration or ensure master nodes are correctly labeled.
Using Gemini Code Assist

The 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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in issue comments and review comments.
Help /gemini help Displays a list of available commands.

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 .gemini/ folder in the base of the repository. Detailed instructions can be found here.

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 or fill out our survey to provide feedback.

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

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@dosubot dosubot bot added the chart Helm Chart label Jul 22, 2025
@oilbeater oilbeater requested a review from zhangzujian July 22, 2025 03:23
Copy link

@gemini-code-assist gemini-code-assist bot left a 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 adds a helpful check to fail the Helm installation if no master nodes are found using the configured labels. The implementation has issues in both charts related to the placement of the check, and an incorrect error message in the kube-ovn-v2 chart. I've left comments with suggestions to address these issues to ensure the feature works as intended and provides clear feedback to users.

@coveralls
Copy link

coveralls commented Jul 22, 2025

Pull Request Test Coverage Report for Build 16433868966

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • 2 unchanged lines in 1 file lost coverage.
  • Overall coverage remained the same at 21.437%

Files with Coverage Reduction New Missed Lines %
pkg/ovs/ovn-nb-logical_router_route.go 2 74.6%
Totals Coverage Status
Change from base Build 16432367515: 0.0%
Covered Lines: 10542
Relevant Lines: 49176

💛 - Coveralls

@dosubot dosubot bot added the lgtm This PR has been approved by a maintainer label Jul 22, 2025
@oilbeater oilbeater merged commit 3602e3a into master Jul 22, 2025
72 checks passed
@oilbeater oilbeater deleted the charts/check branch July 22, 2025 05:45
oilbeater added a commit that referenced this pull request Jul 22, 2025
Signed-off-by: Mengxin Liu <[email protected]>
(cherry picked from commit 3602e3a)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chart Helm Chart lgtm This PR has been approved by a maintainer size:XS This PR changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants