backport of commit a71cdb616567fbcd05c257ba3535d1e2297a9647 (#21445)

Co-authored-by: Jason O'Donnell <2160810+jasonodonnell@users.noreply.github.com>

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

@@ -161,3 +161,5 @@ Affects Vault 1.13.0+
 @include 'update-primary-known-issue.mdx'
 
 @include 'pki-double-migration-bug.mdx'
+
+@include 'update-primary-addrs-panic.mdx'

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

@@ -36,4 +36,4 @@ There are no major changes to announce at this time.
 
 @include 'known-issues/update-primary-data-loss.mdx'
 
-
+@include 'known-issues/update-primary-addrs-panic.mdx'

website/content/partials/known-issues/update-primary-addrs-panic.mdx

@@ -0,0 +1,16 @@
+### Using 'update_primary_addrs' on a demoted cluster causes Vault to panic ((#update-primary-addrs-panic))
+
+#### Affected versions
+
+- 1.13.3, 1.13.4 & 1.14.0
+
+#### Issue
+
+If the [`update_primary_addrs`](/vault/api-docs/system/replication/replication-performance#update_primary_addrs)
+parameter is used on a recently demoted cluster, Vault will panic due to no longer 
+having information about the primary cluster.
+
+#### Workaround
+
+Instead of using `update_primary_addrs` on the recently demoted cluster, instead provide an 
+[activation token](/vault/api-docs/system/replication/replication-performance#token-1).

website/content/partials/update-primary-addrs-panic.mdx

@@ -0,0 +1,16 @@
+### Using 'update_primary_addrs' on a demoted cluster causes Vault to panic ((#update-primary-addrs-panic))
+
+#### Affected versions
+
+- 1.13.3, 1.13.4 & 1.14.0
+
+#### Issue
+
+If the [`update_primary_addrs`](/vault/api-docs/system/replication/replication-performance#update_primary_addrs)
+parameter is used on a recently demoted cluster, Vault will panic due to no longer 
+having information about the primary cluster.
+
+#### Workaround
+
+Instead of using `update_primary_addrs` on the recently demoted cluster, instead provide an 
+[activation token](/vault/api-docs/system/replication/replication-performance#token-1).