Replies: 1 comment
-
Hi @Manfr-edi , this is likely an issue with Vault Eventual Consistency. It's going to be best to first understand your Vault cluster setup, and take a look at the mitigations in that document. On the |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi everyone,
I have an issue on the function for unsealing the vault.
When i call the submit function, the vault reports a log with a "post-unseal setup complete" message, but the python script crashes and give the following error on first access to the vault:
local node not active but active cluster node not found, on get http://192.168.125.55:8200/v1/kv/data/dbsecrets
after this crash, the vault is unsealed, so if i re-run the script, everything is ok.
This is the code i used, the script breakes in the first read_secret_version.
Beta Was this translation helpful? Give feedback.
All reactions