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

VAULT-22569: Handle nil node info when retrieving HA peers #24441

Merged
merged 3 commits into from
Dec 8, 2023

Conversation

miagilepner
Copy link
Contributor

@miagilepner miagilepner commented Dec 8, 2023

Closes #24419

Starting in 1.10 we added a new field to the EchoRequest called NodeInfo. This field gets accessed without a nil check in GetHAPeerNodesCached, which is called by the undo logs watcher.

@miagilepner miagilepner added this to the 1.16.0-rc1 milestone Dec 8, 2023
@github-actions github-actions bot added the hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed label Dec 8, 2023
@miagilepner miagilepner requested review from raskchanky and a team December 8, 2023 14:36
@miagilepner miagilepner marked this pull request as ready for review December 8, 2023 14:36
Copy link

github-actions bot commented Dec 8, 2023

Build Results:
All builds succeeded! ✅

Copy link

github-actions bot commented Dec 8, 2023

CI Results:
All Go tests succeeded! ✅

@miagilepner miagilepner merged commit 9789450 into main Dec 8, 2023
109 checks passed
@miagilepner miagilepner deleted the miagilepner/panic-node-info branch December 8, 2023 16:34
jpenghashi added a commit that referenced this pull request Dec 8, 2023
Due to the reported issue under #24441, we identified that there are users issuing step-down during the upgrade, which is unintended.

We modified the documentation to make it clear that step-down should not be attempted, in addition rephrased the sentence with "step-down" word and exclude that term to avoid confusion.
schavis pushed a commit that referenced this pull request May 1, 2024
Due to the reported issue under #24441, we identified that there are users issuing step-down during the upgrade, which is unintended.

We modified the documentation to make it clear that step-down should not be attempted, in addition rephrased the sentence with "step-down" word and exclude that term to avoid confusion.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed
Projects
None yet
2 participants