-
Notifications
You must be signed in to change notification settings - Fork 4.3k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
a92a303
commit 6f35b56
Showing
1 changed file
with
23 additions
and
0 deletions.
There are no files selected for viewing
23 changes: 23 additions & 0 deletions
23
website/content/partials/known-issues/sync-activation-flags-cache-not-updated.mdx
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,23 @@ | ||
### Cached activation flags for secrets sync on follower nodes are not updated | ||
|
||
#### Affected versions | ||
|
||
- 1.16.0 - 1.16.2 | ||
- 1.17.0 - 1.17.5 | ||
|
||
#### Issue | ||
|
||
Vault 1.16 introduced secrets sync with a one-time flag required to activate the | ||
feature before use. Writing the activation flag to enable secrets sync is forwarded | ||
to leader nodes for storage and distributed to follower nodes, but the in-memory | ||
cache for this flag is not updated on the followers. | ||
|
||
This prevents any secrets sync endpoints (those starting with `sys/sync/`) from | ||
being usable on follower nodes in a cluster. | ||
|
||
#### Workaround | ||
|
||
The cache is force-updated on all nodes when the leader node steps down and the | ||
cluster promotes a new leader. First, activate the secrets sync feature as described | ||
in the [documentation](/vault/docs/sync#activating-the-feature). Then, have the leader node | ||
step down. |