Open person50002 opened 5 months ago
Node1 shows some tls handshake errors. Could you review your certs? Specifically the SAN entries?
Node1 shows some tls handshake errors. Could you review your certs? Specifically the SAN entries?
Are you referring to the following log?
2024-04-08T11:29:22.715Z [INFO] http: TLS handshake error from 127.0.0.1:49832: remote error: tls: bad certificate
I believe this resulted from me trying to to join node 2 without the "-leader-ca-cert=@/vault/config/vault-cert.pem". I then added the option and the join worked, but only manually.
I have also noticed that vault does not write anything to the /vault/file directory, which means that data is not being persisted.
For my own reference, did this work prior to Vault 1.16.0? Thanks!
Describe the bug Configuring retry_join does not trigger vault to join automatically.
To Reproduce
dc1-vault-01 remains the only node in the cluster.
After joining dc1-vault-02 manually, we have 2 nodes, but dc1-vault-03 is still not in the cluster.
Expected behavior Would expect all three nodes to join automatically, instead, I have to manually join each node.
Environment:
Vault server configuration file(s):
dc1-vault-01/config/config.hcl
dc1-vault-02/config/config.hcl
dc1-vault-03/config/config.hcl
Additional context dc1-vault-01 logs:
dc1-vault-02 logs:
dc1-vault-03 logs: