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
probes: use veth device for probing managed neighbor support #25598
Conversation
/test |
/test-1.26-net-next Job 'Cilium-PR-K8s-1.26-kernel-net-next' failed: Click to show.Test Name
Failure Output
Jenkins URL: https://jenkins.cilium.io/job/Cilium-PR-K8s-1.26-kernel-net-next/67/ If it is a flake and a GitHub issue doesn't already exist to track it, comment Then please upload the Jenkins artifacts to that issue. |
net-next is hitting #25524, applying ready-to-merge |
760a834
to
32348dc
Compare
/test |
- Add Timo's update to resolve issue (cilium#25598) Signed-off-by: Fernand <fernand.galiana@isovalent.com>
32348dc
to
fb3b67c
Compare
/test |
Some distributions don't ship with dummy device support/module, leading to the following error when probing for managed neighbors: ``` level=fatal msg="failed to probe managed neighbor support" error="failed to add dummy link: operation not supported" subsys=probes ``` This patch uses a veth device instead, which should be available on nodes running Cilium, if it's not already loaded. Signed-off-by: Timo Beckers <timo@isovalent.com> Reported-by: Fernand Galiana <fernand.galiana@isovalent.com>
fb3b67c
to
fd41f0f
Compare
/test |
/test-1.26-net-next |
Some distributions don't ship with dummy device support/module, leading to the following error when probing for managed neighbors:
This patch uses a veth device instead, which should be available on nodes running Cilium, if it's not already loaded.