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.

Sign up for GitHub

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

Adding common prefix known issue to upgrade guide #6575

Merged
merged 2 commits into from
Apr 17, 2019
Merged

Adding common prefix known issue to upgrade guide #6575

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ef5ef78
Adding common prefix known issue to upgrade guide
chrishoffman Apr 12, 2019
3fbc41e
addressing feedback
chrishoffman Apr 17, 2019
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
8 changes: 8 additions & 0 deletions website/source/docs/upgrading/upgrade-to-0.11.0.html.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,6 +29,14 @@ should work in place of HCL. To work around this error, pretty print the JSON po
or add spaces between repeating brackets. This regression will be addressed in
a future release.

### Common Mount Prefixes

Before running the upgrade, users should run `vault secrets list` to check their mount
table to ensure that mounts do not have common prefix "folders". For example, if there
is a mount with path `team1/` and a mount with path `team1/secrets`, Vault will fail to
unseal. Before upgrade, these mounts must be remounted at a path that does not share a
common prefix.

## Changes Since 0.10.4

### Request Timeouts
Expand Down