-
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
Use of reserved_ports causes job-register evaluations to fail without a reason #1046
Comments
Fixed by 36a7505. Thanks for the great reproduction steps! |
Glad I could help. Thanks for the quick fix! |
@dadgar @cosmopetrich As I undestaned should be present in v0.4.1? However I see the same behavior as described.
Still there's nowhere reason of failure. Removing reserved_ports does the workaround trick and unblocks me, thank you @cosmopetrich! |
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.3.1
Operating system and Environment details
I initially hit the error when testing with 3 server nodes + 2 client nodes bootstrapped via consul, but I'm seeing the same symptoms even with a single node running in both client+server mode without consul.
Issue
Including any reserved_ports entry in the client's reserved block causes evaluations to fail with no indication as to why.
Attempting to run a task that requests too much CPU or memory will work as expected, with Nomad printing a message indicating why it couldn't place the job.
There's some further discussion of the issue on the mailing list, where Diptanu and Parveen helped me figure out what was going on.
Reproduction steps
Bring up the nomad agent with a config along the lines of the following, replacing
PRIVATE_IP
as appropriate.Run nomad with
nomad agent -config /path/to/config.hcl
, wait for the client to become ready innomad node-status
, then run:The evaluation should fail. Removing the
reserved_ports
line and restarting nomad, then re-runningnomad run example.nomad
will cause the evaluation to succeed and a redis:latest container to come up in the local docker instance.Nomad logs
I've uploaded the debug logs for a 3 server + 1 client cluster to this gist. They cover the period from when nomad started till after the evaluation failed.
The logs from the single-server config above are in this gist.
The text was updated successfully, but these errors were encountered: