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

Vault may fail to start after upgrading to kit version 1.6.4 #27

Open

krutten opened this issue Jul 18, 2022 · 1 comment

Contributor

krutten commented Jul 18, 2022

When upgrading from vault-genesis-kit 1.6.2 to 1.6.4 the safe-boshrelease bumps from Consul 0.7.0 to 1.11.3

This causes the Raft version to upgrade from 1 to 3 (see https://www.consul.io/docs/upgrading/upgrade-specific#raft-protocol-version-compatibility)

It is a known issue that a single node Consul may fail to elect a leader after the Raft upgrade, preventing Consul and Vault from starting.

A manual fix is documented at https://learn.hashicorp.com/tutorials/consul/recovery-outage#failure-of-a-single-server-cluster-after-upgrading-raft-protocol and requires making a peers.json file in the /var/vcap/store/vault/consul/raft folder.

The text was updated successfully, but these errors were encountered:

Contributor Author

krutten commented Jul 18, 2022

Issue also created in bosh-release repo cloudfoundry-community/safe-boshrelease#43

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment