-
Notifications
You must be signed in to change notification settings - Fork 6
Fixes for external routing #1176
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
base: master
Are you sure you want to change the base?
Conversation
|
🚀 Temp artifacts published: |
1 similar comment
|
🚀 Temp artifacts published: |
|
I've tested this manually on env-5, and I ran release-test too to check we are not breaking anything: |
|
See #1175 (comment) for an explanation of what we are doing here. As a side note, an upgrade job has failed with a DHCP test failure, probably worth looking into this given the recent changes there @pau-hedgehog @Frostman |
|
@pau-hedgehog could you please take a look at it https://github.com/githedgehog/fabric/actions/runs/19074020190/job/54485354377?pr=1176 ? |
Couldn't find anything relevant in the artifacts: githedgehog/fabricator#1096 |
|
🚀 Temp artifacts published: |
only import prefixes belonging to the external's IPv4 namespace Signed-off-by: Emanuele Di Pascale <emanuele@githedgehog.com>
to ensure we do not overwrite them with routes learned from EVPN peers (e.g. another border leaf attached to the external) Signed-off-by: Emanuele Di Pascale <emanuele@githedgehog.com>
Signed-off-by: Emanuele Di Pascale <emanuele@githedgehog.com>
f58edb0 to
51ba7a7
Compare
|
🚀 Temp artifacts published: |
Fixes #1175