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

docs: add known issues section to 1.9.x upgrade guide #13662

Merged
merged 5 commits into from
Jan 19, 2022
Merged
Changes from 3 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions website/content/docs/upgrading/upgrade-to-1.9.x.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -95,3 +95,13 @@ respects the order of suites given in `tls_cipher_suites`.

See [this blog post](https://go.dev/blog/tls-cipher-suites) for more information.

## Known Issues
- Existing Vault installations that use the [Identity Token
backend](/api-docs/secret/identity/tokens) and have [named
keys](/api-docs/secret/identity/tokens#create-a-named-key) generated will
encounter a panic when any of those existing keys are rotated once passed its
`rotation_period`. This issue affects Vault 1.9.0, and fixed in Vault 1.9.1. The
calvn marked this conversation as resolved.
Show resolved Hide resolved
workarounds for this issue are to either 1) delete any existing keys before the
update, or 2) increase the rotation period to allow ample time for updating past
1.9.0 before a rotation can occur. Workarounds are not necessary if an update to
calvn marked this conversation as resolved.
Show resolved Hide resolved
directly to 1.9.1 or above is performed.