Skip to content

base: update ovn patch #5175

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
Apr 24, 2025
Merged

Conversation

zhangzujian
Copy link
Member

Pull Request

What type of this PR

Examples of user facing changes:

  • Features
  • Bug fixes
  • Docs
  • Tests

Which issue(s) this PR fixes

Fixes #(issue-number)

Signed-off-by: zhangzujian <[email protected]>
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.

Hello @zhangzujian, 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!

Summary of Changes

This pull request updates the OVN patch in the base Dockerfile. The primary change involves updating the commit hash used for the 'northd: add nb option version_compatibility' patch. The old commit hash 625825ef939e543128b6cf48eee9eb79f805713c is replaced with the new commit hash 53d961492036f1d41d9d1b04bab628375a9c6eb5. This update likely incorporates the latest version compatibility features for the northd component.

Highlights

  • OVN Patch Update: The PR updates the OVN patch in the base Dockerfile.
  • Commit Hash Replacement: The commit hash for 'northd: add nb option version_compatibility' is updated from 625825ef939e543128b6cf48eee9eb79f805713c to 53d961492036f1d41d9d1b04bab628375a9c6eb5.
  • Version Compatibility: The update likely incorporates the latest version compatibility features for the northd component.

Changelog

  • dist/images/Dockerfile.base
    • Updated the commit hash for the 'northd: add nb option version_compatibility' patch from 625825ef939e543128b6cf48eee9eb79f805713c to 53d961492036f1d41d9d1b04bab628375a9c6eb5.
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 is currently in preview and 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 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.


A patch applied with care,
Updates the code, beyond compare.
New hash takes its place,
Improving northd's grace,
Compatibility fills the air.

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.

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

The pull request updates the OVN patch in the base Dockerfile. The change involves updating the commit hash for the 'northd: add nb option version_compatibility' patch. The change looks straightforward.

Merge Readiness

The pull request appears to be a simple update of a commit hash. Given the limited scope and the absence of any identified critical or high severity issues, the pull request seems to be in good shape to be merged. However, I am unable to directly approve the pull request, and it is recommended that another reviewer confirm the correctness of the updated patch before merging.

@coveralls
Copy link

Pull Request Test Coverage Report for Build 14632028205

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • 7 unchanged lines in 2 files lost coverage.
  • Overall coverage decreased (-0.02%) to 21.72%

Files with Coverage Reduction New Missed Lines %
pkg/ovs/ovn-nb-bfd.go 2 61.61%
pkg/ovs/ovn-nb-logical_router_route.go 5 75.47%
Totals Coverage Status
Change from base Build 14608160617: -0.02%
Covered Lines: 10249
Relevant Lines: 47187

💛 - Coveralls

@zhangzujian zhangzujian marked this pull request as ready for review April 24, 2025 02:53
@dosubot dosubot bot added the size:XS This PR changes 0-9 lines, ignoring generated files. label Apr 24, 2025
@zhangzujian zhangzujian requested a review from oilbeater April 24, 2025 02:55
@zhangzujian zhangzujian merged commit ab3d11a into kubeovn:master Apr 24, 2025
201 of 205 checks passed
@zhangzujian zhangzujian deleted the update-ovn-patch branch April 24, 2025 06:14
zhangzujian added a commit that referenced this pull request Apr 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
need backport size:XS This PR changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants