-
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
Reserved ports are not honored #9492
Comments
Thanks for reporting @phreakocious , I believe the client port reservations (used for exclusion) currently only apply to static port requests. The dynamic port range is at the moment hard-coded and doesn't take the reservations into account. We'll probably want to take care of this at the same time we enable configurable dynamic port ranges #8186. |
Closed in error and reopened. Thanks for the info. |
Cross-linking #9506 |
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.12.7 (6147cb578794cb2d0c35d68fe1791728a09bb081)
Operating system and Environment details
Debian 10
Issue
Regardless of where
reserved_ports
is specified in theclient
stanza, ports within the range are still allocated. Just in case the documentation for this was incorrect, I tried it as both an inclusive and exclusive range with the same results.Reproduction steps
ensure the nomad.hcl has reserved_ports defined
bring up a new dummy interface with our IPs
restart nomad, run the job
the allocated ports do not seem to reflect either inclusive or exclusive behavior for the reserved_ports ranges
Job file
The text was updated successfully, but these errors were encountered: