Skip to content
This repository has been archived by the owner on Nov 1, 2023. It is now read-only.

vault init does not seem to work #42

Closed
vikashvverma opened this issue Mar 4, 2020 · 4 comments
Closed

vault init does not seem to work #42

vikashvverma opened this issue Mar 4, 2020 · 4 comments
Assignees

Comments

@vikashvverma
Copy link

After login from bastion to vault machine, consul member command works. However when running the vault init after exporting VAULT_ADDRESS, it produces error.

Screenshot 2020-03-04 at 6 46 59 PM

@dcallao
Copy link

dcallao commented Mar 19, 2020

Please use this command instead: vault operator init. See https://www.vaultproject.io/docs/commands/operator/init/

@vikashvverma
Copy link
Author

I used vault operator init as well and it produced the same error except the warning.

@vikashvverma
Copy link
Author

@dcallao Here is the screenshot that this does not seem to work.
Screenshot 2020-05-08 at 3 12 22 PM

@dcallao
Copy link

dcallao commented Jun 15, 2020

@vikashvverma This no longer applies. Vault QSG has been upgraded and initialization works as expected.

@gargana gargana closed this as completed Jun 15, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants