Docs: Update ephemeral logger leak known issue (#24041)

* update known issue

* update known issue partial

* fix links

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

Co-authored-by: Mike Palmiotto <mike.palmiotto@hashicorp.com>

* standardize on sub-loggers

* update known issue

* update versions

* update messaging to include reference to previous known issue

---------

Co-authored-by: Mike Palmiotto <mike.palmiotto@hashicorp.com>
This commit is contained in:
davidadeleon 2023-11-08 14:01:29 -05:00 committed by GitHub
parent ba5f856542
commit 6646eebbc8
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 17 additions and 11 deletions

View File

@ -19,7 +19,7 @@ Version | Issue
All | [API calls to update-primary may lead to data loss](/vault/docs/upgrading/upgrade-to-1.14.x#update-primary-data-loss)
1.14.0+ | [AWS static roles ignore changes to rotation period](/vault/docs/upgrading/upgrade-to-1.14.x#aws-static-role-rotation)
1.14.0+ | [UI Collapsed navbar does not allow certain click events](/vault/docs/upgrading/upgrade-to-1.14.x#ui-collapsed-navbar)
1.14.3+ | [Vault storing references to ephemeral sub-loggers causing memory leak](/vault/docs/upgrading/upgrade-to-1.14.x#ephemeral-loggers-memory-leak)
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)

View File

@ -19,7 +19,7 @@ Version | Issue
1.15.0 | [Panic in AWS auth method during IAM-based login](/vault/docs/upgrading/upgrade-to-1.15.x#panic-in-aws-auth-method-during-iam-based-login)
1.15.0+ | [UI Collapsed navbar does not allow certain click events](/vault/docs/upgrading/upgrade-to-1.15.x#ui-collapsed-navbar)
1.15 | [Vault file audit devices do not honor SIGHUP signal to reload](/vault/docs/upgrading/upgrade-to-1.15.x#file-audit-devices-do-not-honor-sighup-signal-to-reload)
1.15.0+ | [Vault storing references to ephemeral sub-loggers causing memory leak](/vault/docs/upgrading/upgrade-to-1.15.x#ephemeral-loggers-memory-leak)
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)

View File

@ -1,14 +1,20 @@
### 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+
This memory leak affects Vault Community and Enterprise versions:
A fix will be issued in the next release
- 1.13.7 - 1.13.9
- 1.14.3 - 1.14.5
- 1.15.0 - 1.15.1
This change that introduced this leak will be reverted in the next release
#### Issue
Vault is unexpectedly storing references to ephemeral sub-loggers which prevents them from being cleaned up, leading to
a memory leak. This came about from a change to address a previously known issue around [sub-logger levels not being adjusted
on reload](/vault/docs/upgrading/upgrade-to-1.15.x#sublogger-levels-unchanged-on-reload).
This impacts many areas of Vault, but primarily logins in Enterprise.
#### Workaround
There is no workaround.