You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Cannot unseal Vault 1.4.2 with raft storage using only one node.
To Reproduce
Start Vault with Raft storage, create cluster with 1 node and try to unseal.
CLI:
# export VAULT_ADDR=http://0.0.0.0:8200
# vault operator unseal
Unseal Key (will be hidden):
Error unsealing: Error making API request.
URL: PUT http://0.0.0.0:8200/v1/sys/unseal
Code: 500. Errors:
* cannot use unspecified IP with raft storage: 0.0.0.0:8201
UI:
Each attempt of unseal from UI cause this line in log - [WARN] core: cluster listener is already started
Expected behavior
This worked with Vault 1.4.0 and 1.4.1 versions.
From reading the changes in #9008, it doesn't look like a regression. That PR specifically forbids the use of 0.0.0.0 as a cluster address. I'm going to close this, because I don't think there's anything for us to do here.
Describe the bug
Cannot unseal Vault 1.4.2 with raft storage using only one node.
To Reproduce
Start Vault with Raft storage, create cluster with 1 node and try to unseal.
CLI:
UI:
Each attempt of unseal from UI cause this line in log -
[WARN] core: cluster listener is already started
Expected behavior
This worked with Vault 1.4.0 and 1.4.1 versions.
Environment:
Vault 1.4.2
Vault server configuration file(s):
Additional context
It is probably regression from PR 9008.
The text was updated successfully, but these errors were encountered: