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.

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

Backport of Forward PKI revocation requests received by standby nodes to active node into release/1.13.x #19630

Conversation

hc-github-team-secure-vault-core
Copy link
Collaborator

Backport

This PR is auto-generated from #19624 to be assessed for backporting due to the inclusion of the label backport/1.13.x.

WARNING automatic cherry-pick of commits failed. Commits will require human attention.

merge conflict error: POST https://api.github.com/repos/hashicorp/vault/merges: 409 Merge conflict []

The below text is copied from the body of the original PR.


  • A refactoring that occurred in 1.13 timeframe removed what was considered a specific check for standby nodes that wasn't required as a writes should be returning ErrReadOnly.
  • That sadly exposed a long standing bug where the errors from the storage layer were not being properly wrapped, hiding the ErrReadOnly coming from a write and failing the request which causes a failure to forward revocation requests from standby nodes.

Overview of commits

@hashicorp-cla
Copy link

hashicorp-cla commented Mar 20, 2023

CLA assistant check
All committers have signed the CLA.

@hc-github-team-secure-vault-core hc-github-team-secure-vault-core force-pushed the backport/stevendpclark/vault-14665-pki-revocation-standby/publicly-better-mastiff branch 2 times, most recently from 3c17cf7 to e257377 Compare March 20, 2023 14:59
…ode (#19624)

* Forward PKI revocation requests received by standby nodes to active node

 - A refactoring that occurred in 1.13 timeframe removed what was
   considered a specific check for standby nodes that wasn't required
   as a writes should be returning ErrReadOnly.
 - That sadly exposed a long standing bug where the errors from the
   storage layer were not being properly wrapped, hiding the ErrReadOnly
   coming from a write and failing the request.

* Add cl

* Add test for basic PKI operations against standby nodes
@stevendpclark stevendpclark added this to the 1.13.1 milestone Mar 20, 2023
@stevendpclark stevendpclark force-pushed the backport/stevendpclark/vault-14665-pki-revocation-standby/publicly-better-mastiff branch from c36b68d to d767d4c Compare March 20, 2023 15:11
@stevendpclark stevendpclark marked this pull request as ready for review March 20, 2023 15:12
@stevendpclark stevendpclark requested a review from a team March 20, 2023 15:12
@stevendpclark stevendpclark enabled auto-merge (squash) March 20, 2023 15:13
@stevendpclark stevendpclark self-assigned this Mar 20, 2023
…-pki-revocation-standby/publicly-better-mastiff
@stevendpclark stevendpclark merged commit 0b01f09 into release/1.13.x Mar 20, 2023
@stevendpclark stevendpclark deleted the backport/stevendpclark/vault-14665-pki-revocation-standby/publicly-better-mastiff branch March 20, 2023 16:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants