BGP on Minikube tutorial issues #142
Comments
|
Thank you for the bug report! Fixing now, sorry for the hard time! |
Minikube still uses k8s 1.8.0, so it doesn't understand the new API group yet.
…142 The tutorial makes you create test-bgp-router first, and it doesn't work if you don't have the namespace defined.
|
Okay, the last problem is sneaky: alpine:latest updated from bird 1.6 to bird 2.0, but the alpine:latest image cached on my dev machine was still using 1.6... So I didn't notice when the CI built an image with a broken Bird config :( I'm going to have to learn bird 2.0 to fix this. |
|
Okay, ported most of the config over... But Bird 2.0 removed the option to change the BGP listening port, argh! |
|
Alternatively, pin the alpine image version, for consistent builds? ETA: Thanks for looking at this so quickly! ❤️ |
|
That'll work for a short time, but it'll break again when the next version of alpine comes out. Still, it's probably a quick way to fix it for now, while I try to readjust the test router to work with bird2. |
|
Okay, I also cannot pin the version back to 3.6, because Bird is only in the edge repository, so the build is always bird 2.0, and it's no longer compatible with alpine 3.6 :( Plan B: I'm just going to disable Bird and remove it from the test-bgp-router for now, until I can fix it properly. |
|
Debian containers?
…On 17 Jan 2018 08:53, "Dave Anderson" ***@***.***> wrote:
Okay, I also cannot pin the version back to 3.6, because Bird is only in
the edge repository, so the build is always bird 2.0, and it's no longer
compatible with alpine 3.6 :(
Plan B: I'm just going to disable Bird and remove it from the
test-bgp-router for now, until I can fix it properly.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#142 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAVkW9pBZ7O0OBp8i1j-rjymCyA5H-4tks5tLbUmgaJpZM4Rg6b7>
.
|
|
Possibly, but it's way past my bed time and I'm oncall tomorrow, so I just want to release 0.3.1 with a minimal fix and do it right later :) |
Alpine updated their Bird image to 2.0, which breaks the generated config and makes bird behave weirdly in other ways. I need to sleep right now, so this is a quick bandaid while I figure out a real fix.
…142 The tutorial makes you create test-bgp-router first, and it doesn't work if you don't have the namespace defined.
Alpine updated their Bird image to 2.0, which breaks the generated config and makes bird behave weirdly in other ways. I need to sleep right now, so this is a quick bandaid while I figure out a real fix.
|
Okay, MetalLB 0.3.1 released. The manifests should be fixed, and BIRD is disabled for now so that the tutorial works. Container images are still building on CircleCI, so it will take another 5-15min before those are live. I also discovered #143 and #144 while doing the patch version release, so thank you again for the bug report! Closing this bug because the tutorial should work again, but I've opened #145 to track fixing Bird in test-bgp-router. |
|
Container images for 0.3.1 are build and pushed, FYI. |
|
All working as expected now, thank you, now get some sleep 😉 |
OCPBUGS-18985: FRR templates: provide a seqnum for the prefix lists
Is this a bug report or a feature request?:
Bug
What happened:
Attempted to follow the tutorial, failed at Step 2. Failed for the following reasons:
test-bgp-router.yamlmanifest is missing themetallb-systemnamespace definition. Worked around this by creating the namespace manuallytest-bgp-routerpod fails to start, with the following log:What you expected to happen:
Tutorial run through to completion.
How to reproduce it (as minimally and precisely as possible):
Follow the BGP on Minikube tutorial.
Environment:
uname -a): N/AThe text was updated successfully, but these errors were encountered: