-
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
v0.10.4 Unable to deploy job due to "network: no networks available" #7232
Comments
try |
Thanks a lot My curious is
|
I get the same problem with v0.10.4, but it's not there with v0.10.3. Windows Server 2016 |
Thank you for the report. We are digging into this now, but I'm afraid, I'm unable to reproduce. Mind if you provide |
I got this on Windows VMs in Vultr, in case that's useful. I'll try to get a "nomad node status --json" on a host there that's demonstrating the issue. I'll have to spin up a new machine and deploy to it first though. |
I get the same problem with v0.10.4/v0.10.5
And i added
|
@ultra-baba Thanks. Mind if you provide |
@notnoop Same problem for me, working fine with Nomad v0.10.3 but got network error with v0.10.4 & v0.10.5. Here is
Here is
|
@mediarl Thanks for output - that was very helpful! The immediate cause seems to be bad entry in the node status, we'll investigate how it got into that state. Note how $ jq '.Resources.Networks' /tmp/nomad-node-status-0.10.5
[
{
"CIDR": "95.217.132.254/32",
"Device": "eth0",
"DynamicPorts": null,
"IP": "95.217.132.254",
"MBits": 1000,
"Mode": "",
"ReservedPorts": null
},
{
"CIDR": "2a01:4f9:c010:6cc7::1/128",
"Device": "eth0",
"DynamicPorts": null,
"IP": "2a01:4f9:c010:6cc7::1",
"MBits": 1000,
"Mode": "",
"ReservedPorts": null
}
]
$ jq '.NodeResources.Networks' /tmp/nomad-node-status-0.10.5
[
{
"CIDR": "",
"Device": "eth0",
"DynamicPorts": null,
"IP": "",
"MBits": 1000,
"Mode": "",
"ReservedPorts": null
}
] |
@notnoop You welcome! |
@mediarl Thank you very good information. I found the cause! A potential workaround is to set #6779 caused the regression. Looks like hetzner attempts to mimic AWS API, but its implementation is incomplete, so ended up with empty values for local ip addresses and CIDR info!
For comparison, on EC2, the values are:
The regression was due to us accidentally moving to using |
That sounds exactly like what’s happening with Vultr – they (like Hetzner) have an incomplete implementation of the AWS API (the localhost web server URLs).
Josh Clausen
Online and Platform Services Director
505 Games
EDITED to remove email html weird syntax.
|
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.10.4 (f750636)
Operating system and Environment details
ubuntu 18.04 virtualbox
Issue
unable to deploy jobs after upgrading v0.10.4
v0.10.3 does not have this problem
Reproduction steps
start server & client
run job
server.hcl
client.hcl
Job file
https://gist.github.com/guce/1e79f61fd895722c86e968f7acc069a5
Nomad Client logs
https://gist.github.com/guce/e528b16b6efe4446287cb74af85e6b3c
Nomad Server logs
https://gist.github.com/guce/ceacfaaebd65cc616d8ed249edc16e94
The text was updated successfully, but these errors were encountered: