Call to sys/init API results in "core: barrier reports initialized but no seal configuration found"

Vault
,
1

Vault status -

[root@jade-cw01 ~]# curl --insecure -g -s https://[2001:db8:1234::39d5]:8200/v1/sys/seal-status
{“type”:“shamir”,“initialized”:false,“sealed”:true,“t”:0,“n”:0,“progress”:0,“nonce”:"",“version”:"",“migration”:false,“recovery_seal”:false,“storage_type”:“mysql”}

trying to initialize -
[root@jade-cw01 ~]# curl --insecure -g -s --request PUT --data ‘{“secret_shares”: 1, “secret_threshold”: 1}’ https://[2001:db8:1234::39d5]:8200/v1/sys/init
{“errors”:[“core: barrier reports initialized but no seal configuration found”]}

What is going on? I need some help

2

I need some help understanding what is causing that API to return that error?

3

I’m encountering this while experimenting—I’m running Vault with the Consul backend, and I deleted the vault folder from the Consul k/v store.

In older versions of Vault, removing that folder would permit re-initializing Vault with new keys, but now I get the error you’re reporting—so it seems that there’s some “I’m initialized” state either stored elsewhere in Consul, or in one of the Vault nodes themselves.

More research is required, will follow-up once I learn something.

4

Confirmed: removing the entire vault/ key from the Consul kv store (instead of just leaving the key intact and removing the nodes beneath it) lets me re-initialize the Vault.

So it looks like @rishabkatta you might have a a vault key in Consul which is preventing Vault from initializing.

1 Like