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: make route scope relevant for IPv4 only #1829

Merged
merged 1 commit into from
Jan 12, 2022

Conversation

VladoLavor
Copy link
Collaborator

@VladoLavor VladoLavor commented Dec 15, 2021

IPv6 route scope is resolved by the OS and cannot be changed or read by Netlink

  • added e2e test for this and previous Linux L3 plugin fixes

Signed-off-by: Vladimir Lavor vlavor@cisco.com

@VladoLavor VladoLavor self-assigned this Dec 15, 2021
@ondrej-fabry
Copy link
Member

Could you create some e2e tests for this? Ideally with the fix you did before. The e2e tests are better to catch regressions in the future.

@VladoLavor VladoLavor changed the title Make route scope relevant for IPv4 only fix: make route scope relevant for IPv4 only Dec 15, 2021
@VladoLavor VladoLavor force-pushed the master branch 3 times, most recently from 024ddca to fd956d0 Compare January 5, 2022 15:17
* added E2E tests

Signed-off-by: Vladimir Lavor <vlavor@cisco.com>
@ondrej-fabry ondrej-fabry merged commit 27241bb into ligato:master Jan 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants