Docs: known issue - audit file reload on SIGHUP #23608
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 2 commits
October 11, 2023 16:23
…file-sighup-issue
peteski22
added
docs
core/audit
hashicorp-contributed-pr
ncabatoff
reviewed
Oct 11, 2023
website/content/partials/known-issues/1_15-audit-file-sighup-does-not-trigger-reload.mdx
Outdated
Show resolved
Hide resolved
…oes-not-trigger-reload.mdx Co-authored-by: Nick Cabatoff <[email protected]>
ncabatoff
reviewed
Oct 11, 2023
website/content/partials/known-issues/1_15-audit-file-sighup-does-not-trigger-reload.mdx
Outdated
Show resolved
Hide resolved
ncabatoff
reviewed
Oct 11, 2023
website/content/partials/known-issues/1_15-audit-file-sighup-does-not-trigger-reload.mdx
Outdated
Show resolved
Hide resolved
schavis
requested changes
Oct 11, 2023
website/content/partials/known-issues/1_15-audit-file-sighup-does-not-trigger-reload.mdx
Outdated
Show resolved
Hide resolved
website/content/partials/known-issues/1_15-audit-file-sighup-does-not-trigger-reload.mdx
Outdated
Show resolved
Hide resolved
website/content/partials/known-issues/1_15-audit-file-sighup-does-not-trigger-reload.mdx
Outdated
Show resolved
Hide resolved
Comment on lines
23
to
25
| If audit log rotation is a requirement for your Vault deployment, you can use the | ||
| following environment variable set to `true` in order to disable the new underlying | ||
| event framework Vault uses to process audit events. |
There was a problem hiding this comment.
Suggested change
| If audit log rotation is a requirement for your Vault deployment, you can use the | |
| following environment variable set to `true` in order to disable the new underlying | |
| event framework Vault uses to process audit events. | |
| If you use log rotation with `file` audit devices, set the | |
| `VAULT_AUDIT_DISABLE_EVENTLOGGER` environment variable to `true` to disable the | |
| new underlying event framework for | |
| processing audit events: | |
| ```shell-session | |
| $ export VAULT_AUDIT_DISABLE_EVENTLOGGER=true | |
| ``` |
website/content/partials/known-issues/1_15-audit-file-sighup-does-not-trigger-reload.mdx
Outdated
Show resolved
Hide resolved
…oes-not-trigger-reload.mdx Co-authored-by: Sarah Chavis <[email protected]>
schavis
reviewed
Oct 11, 2023
website/content/partials/known-issues/1_15-audit-file-sighup-does-not-trigger-reload.mdx
Outdated
Show resolved
Hide resolved
…oes-not-trigger-reload.mdx Co-authored-by: Sarah Chavis <[email protected]>
…oes-not-trigger-reload.mdx Co-authored-by: Sarah Chavis <[email protected]>
…oes-not-trigger-reload.mdx Co-authored-by: Sarah Chavis <[email protected]>
…oes-not-trigger-reload.mdx Co-authored-by: Sarah Chavis <[email protected]>
schavis
requested changes
Oct 11, 2023
website/content/partials/known-issues/1_15-audit-file-sighup-does-not-trigger-reload.mdx
Outdated
Show resolved
Hide resolved
website/content/partials/known-issues/1_15-audit-file-sighup-does-not-trigger-reload.mdx
Outdated
Show resolved
Hide resolved
website/content/partials/known-issues/1_15-audit-file-sighup-does-not-trigger-reload.mdx
Outdated
Show resolved
Hide resolved
…oes-not-trigger-reload.mdx Co-authored-by: Sarah Chavis <[email protected]>
…oes-not-trigger-reload.mdx Co-authored-by: Sarah Chavis <[email protected]>
ncabatoff
reviewed
Oct 11, 2023
|
|
||
| #### Workaround | ||
|
|
||
| If your Vault cluster uses any `file` audit devices, you can use the following |
There was a problem hiding this comment.
"If your Vault cluster uses any file audit devices" is really about whether you should be worried about the bug, so it probably doesn't belong in the Workaround section.
schavis
approved these changes
Oct 11, 2023
schavis
approved these changes
Oct 11, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Documentation to describe a known issue which has been reported where Vault file audit devices do no honor reopening after Vault processes a
SIGHUPcommand.PR: #23598
Issue: #23596
Release notes: https://vault-git-docs-peteski22audit-file-sighup-issue-hashicorp.vercel.app/vault/docs/release-notes/1.15.0
Upgrade guide: https://vault-git-docs-peteski22audit-file-sighup-issue-hashicorp.vercel.app/vault/docs/upgrading/upgrade-to-1.15.x#file-audit-devices-do-not-honor-sighup-signal-to-reload