-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Nomad v0.6.0-dev arm32v7 "network: no networks available" #3005
Comments
Can you set your clients log level to DEBUG and start it up and provide the logs? |
@dadgar , sorry forgot those, but nothing important there (to me). Here is a replay:
... last 2 lines every 10s. |
Ok, a short follow up [after accepting the fact that Nomad on arm wants to be babysitted] |
Hello guys, I'm having the same issue on amd64, the hosts have 4 ethernet interfaces in bonding mode. After the upgrade from 0.5.6 to 0.6.0, all the allocs stayed, but if we try to plan new ones, we have the same message:
The logs in debug show the following lines:
Wasn't having the issue with the 0.5.6. |
@minusdelta What was the network interfaces configuration on your side? |
@jstoja Absolutely nothing fancy like an 4x aggregation here ... (abbr. vers):
eth0.1816 is a macvlan iface, therefore no ip. Only special things here are:
I observed exactly the same issue with a CoreOS test instance (vm) with only one (v)nic and no macvlan. @dadgar I think the "platform-arm" label doesnt fit anymore here, unfortunately. |
I ran into this problem on Ubuntu 16.04.3 on amd64. I solved this in Nomad 0.6.0 by remembering I use LXC as well and had a bridge interface. Once I switched from the equivalent of eth0 to br0 in the nomad conf file, all was well. |
Any one have a vagrant image or terraform that brings something up to reproduce this? Do not have any raspberry pis lying around. |
@dadgar IMHO most "nomad-on-arm" users (#1693 #2291) != rpi (depending on the model that could also mean |
@minusdelta So you are using "C1" and experiencing this? |
It would seem that this commit might have something to do with it if it's always a link local address. |
This PR changes the fingerprint handling of network interfaces that only contain link local addresses. The new behavior is to prefer globally routable addresses and if none are detected, to fall back to link local addresses if the operator hasn't disallowed it. This gives us pre 0.6 behavior for interfaces with only link local addresses but 0.6+ behavior for IPv6 interfaces that will always have a link-local address. Fixes #3005 /cc diptanuc
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues. |
Nomad version
Nomad v0.6.0-dev c075349 from here #2963 (comment)
Operating system and Environment details
Issue
verify
but on client
even setting it explicitly doesnt help
The text was updated successfully, but these errors were encountered: