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

Fix startup failures when aliases from a pre-1.9 vault version exist #13169

Merged
merged 2 commits into from Nov 16, 2021

Conversation

ncabatoff
Copy link
Contributor

@ncabatoff ncabatoff commented Nov 16, 2021

Add AllowMissing to local_bucket_key schema, preventing startup failures in post-unseal when aliases from an older version exist. Fixes #13158.

…res in post-unseal when aliases from an older version exist.
@vercel vercel bot temporarily deployed to Preview – vault-storybook November 16, 2021 19:40 Inactive
@vercel vercel bot temporarily deployed to Preview – vault November 16, 2021 19:40 Inactive
@ncabatoff ncabatoff merged commit 1f0e0f2 into main Nov 16, 2021
@ncabatoff ncabatoff deleted the allow-local_bucket_key-to-be-missing branch November 16, 2021 19:56
ncabatoff added a commit that referenced this pull request Nov 16, 2021
…13169)

* Add AllowMissing to local_bucket_key schema, preventing startup failures in post-unseal when aliases from an older version exist.
ncabatoff added a commit that referenced this pull request Nov 16, 2021
…13169) (#13171)

* Add AllowMissing to local_bucket_key schema, preventing startup failures in post-unseal when aliases from an older version exist.
@aram535
Copy link
Contributor

aram535 commented Nov 17, 2021

Is there a work around for this or just wait for RC2?

qk4l pushed a commit to qk4l/vault that referenced this pull request Feb 4, 2022
…ashicorp#13169)

* Add AllowMissing to local_bucket_key schema, preventing startup failures in post-unseal when aliases from an older version exist.
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.

failed to update entity in MemDB
3 participants