Docs/vault 7338 retry join known issue (#16540)

* storage/raft: Add known issue for retry_join

* storage/raft: Update known issues with issue reference

* docs: Add return between includes

website/content/docs/upgrading/upgrade-to-1.10.x.mdx

@@ -87,6 +87,8 @@ to understand how the built-in resources are used in the system.
 
 ## Known Issues
 
+@include 'raft-retry-join-failure.mdx'
+
 @include 'raft-panic-old-tls-key.mdx'
 
 ## Errors returned by perf standbys lagging behind active node with Consul storage

website/content/docs/upgrading/upgrade-to-1.11.x.mdx

@@ -18,3 +18,7 @@ path instead of `/_xpack/security` when managing Elasticsearch. If users are on
 an Elasticsearch version prior to 6, they will need to switch back to the old
 API path by setting the [bool config option](/api-docs/secret/databases/elasticdb#use_old_xpack)
 `use_old_xpack=true`.
+
+## Known Issues
+
+@include 'raft-retry-join-failure.mdx'

website/content/partials/raft-retry-join-failure.mdx

@@ -0,0 +1,23 @@
+## Cluster initialization hangs with `retry_join`
+
+The
+[`retry_join`](/docs/concepts/integrated-storage/index#retry_join-configuration)
+feature no longer successfully attempts to rejoin the raft cluster every 2
+seconds following a join failure.
+
+The error occurs when attempting to initialize non-leader nodes with a
+[`retry_join` stanza](/docs/configuration/storage/raft/#retry_join-stanza). This
+affects multi-node raft clusters on [impacted versions](#impacted-versions).
+
+The bug was introduced by commit
+https://github.com/hashicorp/vault/commit/cc6409222ce246ed72d067debe6ffeb8f62f9dad
+and first reported in https://github.com/hashicorp/vault/issues/16486.
+
+### Impacted Versions
+
+Affects versions 1.11.1 and 1.10.5.  Versions prior to these are unaffected.
+
+NOTE: This error does not extend to version 1.9.8, which is slightly different
+in this portion of the code and does not exhibit the same behavior.
+
+New releases addressing this bug are coming soon.