Consul snap restore on a new cluster resulted in "cannot mount under existing mount" during post-unseal #10420
Labels
theme/consul-vault
Relating to Consul & Vault interactions
theme/kv
Issues related to the key value store
type/bug
Feature does not function as expected
Overview of the Issue
A new consul cluster (v 0.8.1) was built to replace current Consul cluster (v 0.8.1). Took the consul snap backup from current cluster and restored it onto the new cluster. During the post-unseal process, the following was observed :
It then goes into a loop and remains in status 429 (standby) :
The current cluster does not show a duplication of mounts :
A side note : I also tried building a new cluster with the latest consul version (1.7.2) and restoring the snapshot with the exact same steps as described below, and I received exactly the same issue. I am doing this activity in preparation of upgrading our current Vault/Consul infrastructure (which is very old!) to the latest versions.
Reproduction Steps
Steps to reproduce this issue, eg:
consul snapshot restore consul.snap.2021-06-15_1200
consul kv delete vault/core/lock
vault operator unseal
Consul info for both Client and Server
Operating system and Environment details
RHEL 8
The text was updated successfully, but these errors were encountered: