Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Set consistency prior to calling CreateSesion #24649

Merged

Conversation

dave92082
Copy link
Contributor

@dave92082 dave92082 commented Dec 29, 2023

Fixes #24648 by setting the consistency level of the cluster prior to creating the session.

Tested using AWS Keyspaces after this fix:

  • Vault Status:
Key                Value
---                -----
Seal Type          shamir
Initialized        true
Sealed             true
Total Shares       3
Threshold          3
Unseal Progress    0/3
Unseal Nonce       n/a
Version            1.16.0-beta1
Build Date         2023-12-29T11:33:31Z
Storage Type       cassandra
HA Enabled         false
  • Startup Log:
==> Vault server configuration:

Administrative Namespace: 
             Api Address: http://127.0.0.1:8200
                     Cgo: disabled
         Cluster Address: https://127.0.0.1:8201
   Environment Variables: AWS_PROFILE, COMMAND_MODE, GO111MODULE, GOFLAGS, HOME, HOMEBREW_CELLAR, HOMEBREW_PREFIX, HOMEBREW_REPOSITORY, INFOPATH, LC_CTYPE, LOGNAME, MANPATH, NVM_BIN, NVM_CD_FLAGS, NVM_DIR, NVM_INC, OLDPWD, PATH, PNPM_HOME, PWD, SHELL, SHLVL, SSH_AUTH_SOCK, TERM, TERMINAL_EMULATOR, TERM_SESSION_ID, TMPDIR, USER, XPC_FLAGS, XPC_SERVICE_NAME, 
              Go Version: go1.21.5
              Listener 1: tcp (addr: "127.0.0.1:8200", cluster address: "127.0.0.1:8201", max_request_duration: "1m30s", max_request_size: "33554432", tls: "disabled")
               Log Level: 
                   Mlock: supported: false, enabled: false
           Recovery Mode: false
                 Storage: cassandra
                 Version: Vault v1.16.0-beta1, built 2023-12-29T11:33:31Z
             Version Sha: 4dace235ced0a69cf447c58a56083aca5861fb74

==> Vault server started! Log data will stream in below:

2023-12-29T11:59:35.786-0800 [INFO]  proxy environment: http_proxy="" https_proxy="" no_proxy=""
2023-12-29T11:59:37.570-0800 [INFO]  incrementing seal generation: generation=1
2023-12-29T11:59:38.073-0800 [INFO]  core: Initializing version history cache for core
2023-12-29T11:59:38.073-0800 [INFO]  events: Starting event system

Copy link
Contributor

@VioletHynes VioletHynes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me. Thanks for the write up and the fix!

@VioletHynes VioletHynes merged commit 52917e0 into hashicorp:main Jan 4, 2024
91 of 93 checks passed
Monkeychip pushed a commit that referenced this pull request Jan 7, 2024
* Set consistency prior to calling CreateSesion

* Add changelog

---------

Co-authored-by: Violet Hynes <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Cassandra backend does not respect the configured consistency level on initial connection
2 participants