-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Error log when trying to find the interface comes without the interface #8345
Milestone
Comments
This was referenced Sep 25, 2023
Closed
Closed
Closed
Merged
Validated on Version:-$ k3s version v1.28.2+k3s-2a9e8e68 (2a9e8e68)
Environment DetailsInfrastructure Node(s) CPU architecture, OS, and Version: Cluster Configuration: Steps to validate the fix
Issue reprodution:There is no interface named test on the node.
-$ curl https://get.k3s.io | INSTALL_K3S_COMMIT=xxxxxxx sh -s - server --cluster-init --flannel-iface=test
Sep 27 sh[17555]: Failed to get unit file state for nm-cloud-setup.service: No such file or directory
Sep 27 k3s[17558]: time="2023-09-27T15:37:58Z" level=warning msg="unable to get global unicast ip from interface name: route ip+net: no such network interface"
Sep 27 k3s[17558]: time="2023-09-27T15:37:58Z" level=fatal msg="invalid node-ip: invalid ip format ''"
Validation Results:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Environmental Info:
K3s Version:
Node(s) CPU architecture, OS, and Version:
Cluster Configuration:
Describe the bug:
If k3s has problems finding the interface, it fails without specifying what interface it is using:
or
This makes debugging difficult
Steps To Reproduce:
Expected behavior:
Logs show the interface
Actual behavior:
Logs don't show the interface
Additional context / logs:
The text was updated successfully, but these errors were encountered: