Adding common prefix known issue to upgrade guide (#6575)

* Adding common prefix known issue to upgrade guide * addressing feedback
hashicorp · Apr 17, 2019 · 5857810 · 5857810
1 parent f20425d
commit 5857810
Showing 1 changed file with 8 additions and 0 deletions.
diff --git a/website/source/docs/upgrading/upgrade-to-0.11.0.html.md b/website/source/docs/upgrading/upgrade-to-0.11.0.html.md
@@ -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` and `vault auth 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