-
Notifications
You must be signed in to change notification settings - Fork 2k
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 v1.5.0-beta.1 panic: SetServer called twice. #16239
Comments
Thanks for trying out the beta and opening this issue @jdoss! This panic looks like it's in the new Task API HTTP server introduced recently in #15864. I'm going to tag-in @schmichael on this, because I know he's still looking at a few related items for GA. |
No problem @tgross! Glad I can help. @schmichael this is very reproducible. I was able to get it to happen again on another node too. The only gotcha might be that I am running two nodes, both as servers and clients. |
Thanks so much for the report @jdoss! I suspect it's the reloading (SIGHUP) that's triggering it. I'll get right on it and the fix will be in 1.5-rc1 coming out 🔜 |
* agent: only reload HTTP servers that use TLS * shutdown task api before client and improve names Fixes #16239
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 v1.5.0-beta.1 (3d735e7)
Operating system and Environment details
Issue
I use smallstep's Certificate Manager to automate my internal PKI for my Nomad cluster and I am testing out Nomad v1.5.0-beta.1 and I noticed Nomad panicked after I renewed my short lived TLS cert and systemd restarted nomad.
Reproduction steps
Renew PKI TLS cert, hup nomad via systemd.
Expected Result
No panic.
Actual Result
A cute panic.
Nomad Server logs (if appropriate)
The text was updated successfully, but these errors were encountered: