-
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 client errors when server bootstrap value is set but server enabled is false #6044
Comments
logs of client failure on startup and working after removal of the server section from the configuration
|
Hey there Since this issue hasn't had any activity in a while - we're going to automatically close it in 30 days. If you're still seeing this issue with the latest version of Nomad, please respond here and we'll keep this open and take another look at this. Thanks! |
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.9.3 (c5e8b66c3789e4e7f9a83b4e188e9a937eea43ce)
Operating system and Environment details
Red Hat Enterprise Linux Server release 7.6 (Maipo)
Issue
Nomad-client fails to start with https://www.nomadproject.io/docs/configuration/server.html#enabled is set to false.
It should startup properly and ignore the entire server section if this flag is set false.
I can circumvent the issue but was surprised to encounter this.
Reproduction steps
Nomad works after removal the server section from the /etc/nomad.d/client.hcl configuration. It appears enabled=false is ignored by the agent to warrant this removal.
The text was updated successfully, but these errors were encountered: