Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Backport of Add note about cross-cluster write failures into release/1.13.x #20507

Merged
merged 1 commit into from
May 4, 2023
Merged

Backport of Add note about cross-cluster write failures into release/1.13.x #20507

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 21 additions & 0 deletions website/content/docs/upgrading/upgrade-to-1.13.x.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -106,3 +106,24 @@ accommodates the default minimum duration of an STS token and overrides the defa
#### Impacted Versions

Affects Vault 1.13.0 only.


### PKI Cross-Cluster Revocation Requests and Unified CRL/OCSP

When revoking certificates on a cluster that doesn't own the
certificate, writing the revocation request will fail with
a message like `error persisting cross-cluster revocation request`.
Similar errors will appear in the log for failure to write
unified CRL and unified delta CRL WAL entries.

As a workaround, submit revocation requests to the cluster which
issued the certificate, or use BYOC revocation. Use cluster-local
OCSP and CRLs until this is resolved.

#### Impacted Versions

Affects Vault 1.13.0 to 1.13.2. Fixed in 1.13.3.

On upgrade, all local revocations will be synchronized between
clusters; revocation requests are not persisted when failing to
write cross-cluster.