Add known issue for sublogger memory leak (#23977) (#24008)

* add known issue for sublogger memory leak

* update known issue

* Update website/content/partials/known-issues/ephemeral-loggers-memory-leak.mdx



* Update website/content/partials/known-issues/ephemeral-loggers-memory-leak.mdx



* Update website/content/partials/known-issues/ephemeral-loggers-memory-leak.mdx



---------

Co-authored-by: davidadeleon <56207066+davidadeleon@users.noreply.github.com>
Co-authored-by: Hamid Ghaf <83242695+hghaf099@users.noreply.github.com>
Co-authored-by: Jason O'Donnell <2160810+jasonodonnell@users.noreply.github.com>
Co-authored-by: Brian Kassouf <briankassouf@users.noreply.github.com>
This commit is contained in:
hc-github-team-secure-vault-core 2023-11-03 17:04:47 -04:00 committed by GitHub
parent 4fab8c18f5
commit 759b1a7c02
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
5 changed files with 27 additions and 5 deletions

View File

@ -122,6 +122,8 @@ The fix for this UI issue is coming in the Vault 1.13.1 release.
@include 'known-issues/internal-error-namespace-missing-policy.mdx'
@include 'known-issues/ephemeral-loggers-memory-leak.mdx'
## Feature deprecations and EOL
Please refer to the [Deprecation Plans and Notice](/vault/docs/deprecation) page

View File

@ -13,7 +13,7 @@ description: |-
## Known issues and breaking changes
Version | Issue
Version | Issue
------- | ------------------------------------------------------------
1.14.0+ | [Users limited by control groups can only access issuer detail from PKI overview page](/vault/docs/upgrading/upgrade-to-1.14.x#ui-pki-control-groups)
All | [API calls to update-primary may lead to data loss](/vault/docs/upgrading/upgrade-to-1.14.x#update-primary-data-loss)
@ -83,7 +83,7 @@ Follow the learn more links for more information, or browse the list of
</tr>
</thead>
<tbody>
<tr>
<td rowspan={2} style={{verticalAlign: 'middle'}}>
Public Key Infrastructure (PKI)
@ -105,7 +105,7 @@ Follow the learn more links for more information, or browse the list of
Use the improved PKI web UI to manage your PKI instance with intuitive
configuration and reasonable defaults for workflows, metadata, issuer
info, mount and tidy configuration, cross signing, multi-issuers etc.and
includes.
includes.
<br /><br />
Learn more:&nbsp;
<a href="/vault/api-docs/secret/pki#acme-certificate-issuance">PKI Secrets Engine</a>
@ -241,14 +241,14 @@ Follow the learn more links for more information, or browse the list of
</tr>
</thead>
<tbody>
<tr>
<td style={{verticalAlign: 'middle'}}>
Vault replication
</td>
<td style={{verticalAlign: 'middle', textAlign: 'center'}}>ENHANCED</td>
<td style={{verticalAlign: 'middle'}}>
Stability improvements based on customer feedback for Vault 1.13. See the
Stability improvements based on customer feedback for Vault 1.13. See the
<a href="https://raw.githubusercontent.com/hashicorp/vault/main/CHANGELOG.md">
Vault changelog
</a>
@ -278,6 +278,8 @@ Follow the learn more links for more information, or browse the list of
@include 'known-issues/internal-error-namespace-missing-policy.mdx'
@include 'known-issues/ephemeral-loggers-memory-leak.mdx'
## Feature deprecations and EOL
Deprecated in 1.14 | Retired in 1.14

View File

@ -184,3 +184,5 @@ Affects Vault 1.13.0+
@include 'known-issues/transit-managed-keys-panics.mdx'
@include 'known-issues/internal-error-namespace-missing-policy.mdx'
@include 'known-issues/ephemeral-loggers-memory-leak.mdx'

View File

@ -52,3 +52,5 @@ is measuring cumulative time writing, and not the distribution of individual wri
@include 'known-issues/transit-managed-keys-sign-fails.mdx'
@include 'known-issues/internal-error-namespace-missing-policy.mdx'
@include 'known-issues/ephemeral-loggers-memory-leak.mdx'

View File

@ -0,0 +1,14 @@
### Vault is storing references to ephemeral sub-loggers leading to a memory leak
Vault is unexpectedly storing references to ephemeral sub-loggers which prevents them from being cleaned up, leading to
a memory leak. This impacts many areas of Vault, but primarily logins in Enterprise.
There is no workaround.
#### Affected versions
This issue affects Vault Community and Enterprise versions:
- 1.13.7+
- 1.14.3+
- 1.15.0+
A fix will be issued in the next release