From d3bed43f4092eeddb40803308d6b2517413734cd Mon Sep 17 00:00:00 2001 From: davidadeleon <56207066+davidadeleon@users.noreply.github.com> Date: Wed, 8 Nov 2023 18:40:50 -0500 Subject: [PATCH] Docs: Add expiration metrics fatal error known issue (#24050) * add expiration metrics fatal error known issue * adjust expected fix releases * provide more clarity around issue --- website/content/docs/release-notes/1.13.0.mdx | 2 ++ website/content/docs/release-notes/1.14.0.mdx | 3 +++ website/content/docs/release-notes/1.15.0.mdx | 4 ++++ .../docs/upgrading/upgrade-to-1.13.x.mdx | 2 ++ .../docs/upgrading/upgrade-to-1.14.x.mdx | 2 ++ .../docs/upgrading/upgrade-to-1.15.x.mdx | 2 ++ .../expiration-metrics-fatal-error.mdx | 22 +++++++++++++++++++ 7 files changed, 37 insertions(+) create mode 100644 website/content/partials/known-issues/expiration-metrics-fatal-error.mdx diff --git a/website/content/docs/release-notes/1.13.0.mdx b/website/content/docs/release-notes/1.13.0.mdx index 4da002e2ed..eea72204d1 100644 --- a/website/content/docs/release-notes/1.13.0.mdx +++ b/website/content/docs/release-notes/1.13.0.mdx @@ -126,6 +126,8 @@ The fix for this UI issue is coming in the Vault 1.13.1 release. @include 'known-issues/sublogger-levels-unchanged-on-reload.mdx' +@include 'known-issues/expiration-metrics-fatal-error.mdx' + ## Feature deprecations and EOL Please refer to the [Deprecation Plans and Notice](/vault/docs/deprecation) page diff --git a/website/content/docs/release-notes/1.14.0.mdx b/website/content/docs/release-notes/1.14.0.mdx index 6f0124d35d..5aa8e128f2 100644 --- a/website/content/docs/release-notes/1.14.0.mdx +++ b/website/content/docs/release-notes/1.14.0.mdx @@ -22,6 +22,7 @@ All | [API calls to update-primary may lead to data loss](/vault/docs/upgrad 1.14.3+ | [Vault storing references to ephemeral sub-loggers causing memory leak](/vault/docs/upgrading/upgrade-to-1.14.x#vault-is-storing-references-to-ephemeral-sub-loggers-leading-to-a-memory-leak) 1.14.4+ | [Internal error when vault policy in namespace does not exist](/vault/docs/upgrading/upgrade-to-1.14.x#internal-error-when-vault-policy-in-namespace-does-not-exist) 1.14.0+ | [Sublogger levels not adjusted on reload](/vault/docs/upgrading/upgrade-to-1.14.x#sublogger-levels-unchanged-on-reload) +1.14.5 | [Fatal error during expiration metrics gathering causing Vault crash](/vault/docs/upgrading/upgrade-to-1.15.x#fatal-error-during-expiration-metrics-gathering-causing-vault-crash) ## Vault companion updates @@ -284,6 +285,8 @@ Follow the learn more links for more information, or browse the list of @include 'known-issues/ephemeral-loggers-memory-leak.mdx' +@include 'known-issues/expiration-metrics-fatal-error.mdx' + ## Feature deprecations and EOL Deprecated in 1.14 | Retired in 1.14 diff --git a/website/content/docs/release-notes/1.15.0.mdx b/website/content/docs/release-notes/1.15.0.mdx index e522dc6212..b96e80c364 100644 --- a/website/content/docs/release-notes/1.15.0.mdx +++ b/website/content/docs/release-notes/1.15.0.mdx @@ -22,6 +22,8 @@ Version | Issue 1.15.0+ | [Vault storing references to ephemeral sub-loggers causing memory leak](/vault/docs/upgrading/upgrade-to-1.15.x#vault-is-storing-references-to-ephemeral-sub-loggers-leading-to-a-memory-leak) 1.15.0+ | [Internal error when vault policy in namespace does not exist](/vault/docs/upgrading/upgrade-to-1.15.x#internal-error-when-vault-policy-in-namespace-does-not-exist) 1.15.0+ | [Sublogger levels not adjusted on reload](/vault/docs/upgrading/upgrade-to-1.15.x#sublogger-levels-unchanged-on-reload) +1.15.1 | [Fatal error during expiration metrics gathering causing Vault crash](/vault/docs/upgrading/upgrade-to-1.15.x#fatal-error-during-expiration-metrics-gathering-causing-vault-crash) + ## Vault companion updates @@ -247,6 +249,8 @@ Follow the learn more links for more information, or browse the list of @include 'known-issues/ephemeral-loggers-memory-leak.mdx' +@include 'known-issues/expiration-metrics-fatal-error.mdx' + ## Feature deprecations and EOL Deprecated in 1.15 | Retired in 1.15 diff --git a/website/content/docs/upgrading/upgrade-to-1.13.x.mdx b/website/content/docs/upgrading/upgrade-to-1.13.x.mdx index 4fbb952461..6b866410fa 100644 --- a/website/content/docs/upgrading/upgrade-to-1.13.x.mdx +++ b/website/content/docs/upgrading/upgrade-to-1.13.x.mdx @@ -188,3 +188,5 @@ Affects Vault 1.13.0+ @include 'known-issues/ephemeral-loggers-memory-leak.mdx' @include 'known-issues/sublogger-levels-unchanged-on-reload.mdx' + +@include 'known-issues/expiration-metrics-fatal-error.mdx' diff --git a/website/content/docs/upgrading/upgrade-to-1.14.x.mdx b/website/content/docs/upgrading/upgrade-to-1.14.x.mdx index 72c415114e..a04fd0f1f2 100644 --- a/website/content/docs/upgrading/upgrade-to-1.14.x.mdx +++ b/website/content/docs/upgrading/upgrade-to-1.14.x.mdx @@ -58,3 +58,5 @@ is measuring cumulative time writing, and not the distribution of individual wri @include 'known-issues/ephemeral-loggers-memory-leak.mdx' @include 'known-issues/sublogger-levels-unchanged-on-reload.mdx' + +@include 'known-issues/expiration-metrics-fatal-error.mdx' diff --git a/website/content/docs/upgrading/upgrade-to-1.15.x.mdx b/website/content/docs/upgrading/upgrade-to-1.15.x.mdx index 2654fe46de..6b246528d3 100644 --- a/website/content/docs/upgrading/upgrade-to-1.15.x.mdx +++ b/website/content/docs/upgrading/upgrade-to-1.15.x.mdx @@ -62,3 +62,5 @@ option. @include 'known-issues/ephemeral-loggers-memory-leak.mdx' @include 'known-issues/sublogger-levels-unchanged-on-reload.mdx' + +@include 'known-issues/expiration-metrics-fatal-error.mdx' diff --git a/website/content/partials/known-issues/expiration-metrics-fatal-error.mdx b/website/content/partials/known-issues/expiration-metrics-fatal-error.mdx new file mode 100644 index 0000000000..b8aa058718 --- /dev/null +++ b/website/content/partials/known-issues/expiration-metrics-fatal-error.mdx @@ -0,0 +1,22 @@ +### Fatal error during expiration metrics gathering causing Vault crash + +#### Affected versions + +This issue affects Vault Community and Enterprise versions: +- 1.13.9 +- 1.14.5 +- 1.15.1 + +A fix will be issued in Vault 1.13.10, 1.14.6, and 1.15.2. + +#### Issue + +A recent change to Vault to improve state change speed (e.g. becoming active or standby) introduced a concurrency issue +which can lead to a concurrent iteration and write on a map, causing a fatal error and crashing Vault. This error occurs +when gathering lease and token metrics from the expiration manager. These metrics originate from the active node in a HA +cluster, as such a standby node will take over active duties and the cluster will remain functional should the original +active node encounter this bug. The new active node will be vulnerable to the same bug, but may not encounter it immediately. + +There is no workaround. + +