-
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 1.0.1 client segfaults on startup with Consul 1.8.3 #9738
Comments
Thanks for reporting @cb22, I was able to reproduce this like you described by launching a Nomad v0.12.9, creating a connect job, and restarting Nomad on v1.0.1 (avoiding FWIW in the upgrade guide we do recommend doing node drains and upgrading to Nomad v1.0.0+ and Consul 1.9.0+ concurrently to ensure a smooth transition. However we certainly shouldn't panic on the in-place upgrade path either. |
When upgrading from Nomad v0.12.x to v1.0.x, Nomad client will panic on startup if the node is running Connect enabled jobs. This is caused by a missing piece of plumbing of the Consul Proxies API interface during the client restore process. Fixes #9738
When upgrading from Nomad v0.12.x to v1.0.x, Nomad client will panic on startup if the node is running Connect enabled jobs. This is caused by a missing piece of plumbing of the Consul Proxies API interface during the client restore process. Fixes #9738
When upgrading from Nomad v0.12.x to v1.0.x, Nomad client will panic on startup if the node is running Connect enabled jobs. This is caused by a missing piece of plumbing of the Consul Proxies API interface during the client restore process. Fixes #9738
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
Server: Nomad v1.0.1 (c9c68aa)
Client: Nomad v1.0.1 (c9c68aa) (was, 0.12.9) + Consul 1.8.3
Operating system and Environment details
Debian 10, official Nomad packages
Issue
After upgrading the server from 0.12 to 1.0 (which went smoothly), I tried to upgrade a client node that was running Consul 1.8.3 and had Consul Connect enabled jobs scheduled on it.
After doing a
apt install nomad && systemctl restart nomad
, it would panic - presumably trying to look up which versions of Envoy are supported and failing.Downgrading the client back to 0.12 worked OK, as did manually specifying the version of Envoy to use (I feel that upgrading Consul would have done the trick too):
The upgrade guide mentions that it should do this automatically:
Nomad Client logs (if appropriate)
The text was updated successfully, but these errors were encountered: