#28682·vault

Secret engine not being disabled

Author: samuelvgoCreated Oct 11, 2024Updated Sep 21, 2026
Labelsquestion

Describe the bug Vault is unable to disable completely a secret engine, which is now stuck in the middle of not being usable anymore and not completely disabled.

To Reproduce Steps to reproduce the behavior:

  1. Login to vault
  2. Run vault secrets disable /path/to/secret/engine
  3. See error: error":"1 error occurred:\n\t* invalid request\n\n"}

Expected behavior It was expected that secret engine would be completely disabled.

Environment:

  • Vault Server Version (retrieve with vault status): Version 1.15.6
  • Vault CLI Version (retrieve with vault version): Vault v1.15.6 (615cf6f1dce9aa91bc2035ce33b9f689952218f0), built 2024-02-28T17:07:34Z
  • Server Operating System/Architecture: Debian GNU/Linux 12 (bookworm)

Vault server configuration file(s):

hcl
listener "tcp" {
  address       = "10.100.32.73:8200"
  tls_cert_file = "/etc/vault.d/ssl/certs/vault-server-cert.pem"
  tls_key_file  = "/etc/vault.d/ssl/private_keys/vault-server-key.pem"
  tls_cipher_suites = "TLS_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_AES_256_CBC_SHA,TLS_RSA_WITH_AES_128_GCM_SHA256,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_AES_128_GCM_SHA256,TLS_AES_256_GCM_SHA384,TLS_CHACHA20_POLY1305_SHA256,TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384"
}
listener "tcp" {
  address       = "127.0.0.1:8200"
  tls_disable   = true
  max_request_duration = "900s"
}
storage "raft" {
  path = "/var/lib/vault"
  node_id = "hcvault-cde-cde-europe-west4-z44s"
}
service_registration "consul" {
  address = "127.0.0.1:8500"
  token = "
  service = "cdevault"
}
cluster_addr = "http://10.100.32.73:8201"
api_addr = "http://10.100.32.73:8200"
ui = true

Additional context The vault server was version 1.14.10, and recently updated to version 1.15.6. The disable initially was triggered via UI, and the secret engine had a significant number of records, with around 21499 pages in the search via UI.

Nothing with that secret engine works anymore, and the vault disable is failing constantly with:

Vault audit: delete failed - reason: 1 error occurred: * invalid request

And when trying to create a secret it says:

route entry is tainted.

We have tried the leases force removal but it also didn't work