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
Hi,
I started encountering this bug and unfortunately I wasn't able to track when it was introduced.
I have a cli/tui that interacts with vault, however it started failing doing a health check to get version to do the initial setup.
The idea is to check if the vault instance is enterprise one and do a setup depending on it
The code block is straight forward:
cfg := api.DefaultConfig()
cfg.Address = vaultyCfg.VaultAddr
tlsCfg := &api.TLSConfig{}
if vaultyCfg.VaultCaCert != "" {
tlsCfg.CACert = vaultyCfg.VaultCaCert
}
if vaultyCfg.VaultClientCert != "" {
tlsCfg.ClientCert = vaultyCfg.VaultClientCert
}
if vaultyCfg.VaultClientKey != "" {
tlsCfg.ClientKey = vaultyCfg.VaultClientKey
}
err := cfg.ConfigureTLS(tlsCfg)
if err != nil {
log.Error().Err(err).Msgf("Failed to configure TLS: %v", err)
return err
}
client, err := api.NewClient(cfg)
if err != nil {
log.Error().Err(err).Msg("Failed to create Vault client")
return err
}
client.SetToken(vaultyCfg.VaultToken)
// Check if the client is successfully created by making a request to Vault
health, err := client.Sys().Health()
if err != nil {
log.Error().Err(err).Msg("Failed to do healthcheck with Vault")
return err
}
However this is currently resulting in:
Failed to start Vault client: Error making API request.
Namespace: myns/
URL: GET https://<myURL>/v1/sys/health?drsecondarycode=299&performancestandbycode=299&sealedcode=299&standbycode=299&uninitcode=299
Code: 404. Errors:
* unsupported path
exit status 1
I've tried against a HCP Vault instance and a local dev server - no issue.
However the moment I try against a the vault instances we have configured I run into this issue. Is there something that
To Reproduce
Code block is above. Try to access the /v1/sys/health endpoint
Describe the bug
Hi,
I started encountering this bug and unfortunately I wasn't able to track when it was introduced.
I have a cli/tui that interacts with vault, however it started failing doing a health check to get version to do the initial setup.
The idea is to check if the vault instance is enterprise one and do a setup depending on it
The code block is straight forward:
However this is currently resulting in:
I've tried against a HCP Vault instance and a local dev server - no issue.
However the moment I try against a the vault instances we have configured I run into this issue. Is there something that
To Reproduce
Code block is above. Try to access the
/v1/sys/health
endpointExpected behavior
To receive a HealthResponse correctly
Environment:
vault status
): 1.15.4+entThe text was updated successfully, but these errors were encountered: