Skip to content
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

Update to raft lib v1.3.3 #13703

Merged
merged 2 commits into from
Jan 24, 2022
Merged

Update to raft lib v1.3.3 #13703

merged 2 commits into from
Jan 24, 2022

Conversation

ncabatoff
Copy link
Collaborator

@ncabatoff ncabatoff commented Jan 19, 2022

I have manually tested - with both OSS and ENT - upgrading from a 3-node Vault 1.9.2 cluster to a vault binary including this change. I used the standard minimal-downtime upgrade procedure wherein each standby node is replaced in turn, followed by the leader. After upgrading I verified that vault was healthy by sending a bunch of writes to it and checking the autopilot and leader status endpoints (also via log inspection).

Also note re the changelog entry: we haven't seen any instances of this Raft bug in Vault yet, but Consul has, and we're definitely vulnerable to them in theory.

@ncabatoff ncabatoff requested a review from a team January 19, 2022 15:35
@ncabatoff ncabatoff added this to the 1.7.9 milestone Jan 19, 2022
@vercel vercel bot temporarily deployed to Preview – vault January 19, 2022 20:48 Inactive
@vercel vercel bot temporarily deployed to Preview – vault-storybook January 19, 2022 20:48 Inactive
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants