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
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
Vault running with integrated storage, single node is fine. But this will also render an entire cluster unusable the same manner as it won't elect a leader.
Set cache-config per https://www.vaultproject.io/api/secret/transit#configure-cache $ vault write transit/cache-config size=1 WARNING! The following warnings were returned from Vault: * cache configurations will be applied when this backend is restarted
Restart vault service
Node cannot complete full startup. See bottom of issue for full log.
2021-07-13T20:44:00.394Z [ERROR] core: failed to create mount entry: path=transit/ error="failed to create cache: Must provide a positive size"
2021-07-13T20:44:00.394Z [INFO] core: pre-seal teardown starting
2021-07-13T20:44:00.394Z [INFO] core: stopping raft active node
2021-07-13T20:44:00.394Z [INFO] core: stopping replication
2021-07-13T20:44:00.394Z [INFO] core: closed sync connection
2021-07-13T20:44:00.394Z [INFO] core: replication stopped
Expected behavior
Regardless of cache-config setting, node and cluster are stable.
Environment:
Vault Server Version (retrieve with vault status): 1.7.3+ent
Vault CLI Version (retrieve with vault version): 1.7.3+ent
Server Operating System/Architecture: Ubuntu 18 LTS
Vault server configuration file(s):
# Paste your Vault config here.# Be sure to scrub any sensitive values
Additional context
Running $ vault read transit/cache-config
shows No value found at transit/cache-config
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
$ vault secrets enable transit
Success! Enabled the transit secrets engine at: transit/
$ vault write transit/cache-config size=1
WARNING! The following warnings were returned from Vault:
* cache configurations will be applied when this backend is restarted
Expected behavior
Regardless of cache-config setting, node and cluster are stable.
Environment:
vault status
): 1.7.3+entvault version
): 1.7.3+entVault server configuration file(s):
Additional context
Running
$ vault read transit/cache-config
shows
No value found at transit/cache-config
More log:
The text was updated successfully, but these errors were encountered: