-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Problem upgrading from 1.6.2 to 1.7.1 #7395
Comments
Hi @i0rek just fount out what happened. In the commit 7b471f6 a field of the struct SessionSpecificRequest was renamed so when talking between nodes in differents versions this fails. I fixed it by doing the following:
|
@jorgemarey I am looking into this. The code you linked does look correct but we must have missed another place where the deprecated field is used. The intention with that commit was to fixup the RPC struct when it makes it to the server. So that users don't run into this exact issue. |
@jorgemarey I totally misread your post before. I thought you were linking to a commit with those changes rather than showing the necessary changes to fix the issue. Look for this to be fixed in v1.7.2 |
Great. Thanks! |
Overview of the Issue
We have a cluster of consul with the 1.6.2 version. We tried to upgrade to 1.7.1 but the following happen after upgrading the servers (we use consul-esm and vault in the cluster):
Seems like they couldn't perform the lock.
Also, in the nodes we see the following:
After upgrading the node to 1.7.1 the problems seems to go away.
I tested this in a development environment, but when we release this to producción where we have hundreds of nodes we can't have this failling until we upgrade all nodes.
Any thoughts?
Thanks!
The text was updated successfully, but these errors were encountered: