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

vxlan network logs coming from flannel not being propagated #8912

Open
manuelbuil opened this issue Nov 20, 2023 · 4 comments
Open

vxlan network logs coming from flannel not being propagated #8912

manuelbuil opened this issue Nov 20, 2023 · 4 comments
Assignees

Comments

@manuelbuil
Copy link
Contributor

Environmental Info:
K3s Version:

Any

Node(s) CPU architecture, OS, and Version:

Cluster Configuration:

Describe the bug:

When there is an error in the creation of vxlan infrastructure, the error is not propagated to k3s or sent to journalctl, hence we are blind. E.g. #8794

Steps To Reproduce:

  • Installed K3s:

Expected behavior:

Actual behavior:

Additional context / logs:

@thomasferrandiz
Copy link
Contributor

when running k3s, I can see logs coming from flannel like this line:

I1120 15:12:37.814046    3322 kube.go:510] Creating the node lease for IPv4. This is the n.Spec.PodCIDRs: [10.42.0.0/24]

so I guess it's more an issue internal to flannel for some specific errors?

@manuelbuil
Copy link
Contributor Author

when running k3s, I can see logs coming from flannel like this line:

I1120 15:12:37.814046    3322 kube.go:510] Creating the node lease for IPv4. This is the n.Spec.PodCIDRs: [10.42.0.0/24]

so I guess it's more an issue internal to flannel for some specific errors?

Ah nice! Thanks Thomas! Yeah, then it is probably a flannel issue not logging problems when trying to create the ip route and not working well (at least in ipv6)

@thomasferrandiz
Copy link
Contributor

if there is an error when adding the ipv6 route it should be logged here:
https://github.com/flannel-io/flannel/blob/c498d00a87d394d9df16cd4fc303a8ea6d83063f/pkg/backend/vxlan/vxlan_network.go#L264
Or maybe netlink doesn't return an error but fails silently in some cases?

Otherwise the issue could be that the flannel message is drowned in all the other logs.

@manuelbuil
Copy link
Contributor Author

if there is an error when adding the ipv6 route it should be logged here: https://github.com/flannel-io/flannel/blob/c498d00a87d394d9df16cd4fc303a8ea6d83063f/pkg/backend/vxlan/vxlan_network.go#L264 Or maybe netlink doesn't return an error but fails silently in some cases?

Otherwise the issue could be that the flannel message is drowned in all the other logs.

Probably there is a silent failure...

@caroline-suse-rancher caroline-suse-rancher moved this from New to In Triage in K3s Development Jan 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In Triage
Development

No branches or pull requests

2 participants