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

Vault backup and restore fail if s3 secret key contains # character #199

Closed
fdlk opened this issue Aug 26, 2019 · 1 comment
Closed

Vault backup and restore fail if s3 secret key contains # character #199

fdlk opened this issue Aug 26, 2019 · 1 comment
Labels
bug Something isn't working chart-vault Vault helm chart

Comments

@fdlk
Copy link
Contributor

fdlk commented Aug 26, 2019

Which chart are you referring?

How to reproduce

Create a minio with secret key equal to mr2Xc^y#AWTZ92NWJ#m^NBABZ!js&M#hPqRmD4ps
Deploy a vault with that minio as backup store.
Try to restore from the minio.

Expected behavior

The restore succeeds, vault can be unsealed.

Observed behavior

Restore says it was completed, but restore operator log shows that Signature does not match and vault status and vault init complain that the vault is not initialized.

@fdlk fdlk added bug Something isn't working chart-vault Vault helm chart labels Aug 26, 2019
fdlk added a commit to fdlk/molgenis-ops-helm that referenced this issue Aug 26, 2019
If the s3 credentials contain special characters, the backup and restore will fail.
Add a description to warn the user about this.

This is a workaround for molgenis#199
@fdlk
Copy link
Contributor Author

fdlk commented Aug 26, 2019

Caused by coreos/etcd-operator#2114

@fdlk fdlk closed this as completed May 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working chart-vault Vault helm chart
Projects
None yet
Development

No branches or pull requests

1 participant