Error disabling the plugin

Question

Error disabling the plugin

bbaassssiiee opened this issue 5 years ago · 9 comments

Vault 1.2.2
plugin: 0.0.4

Answer 1 · 2019-09-27T15:08:25.000Z

Hmm. What happens if you try to disable the plugin via the CLI?

Answer 2 · 2019-09-27T15:11:59.000Z

[vagrant@server01 ~]$ /usr/local/bin/vault secrets disable gen/
Error disabling secrets engine at gen/: Error making API request.

URL: DELETE https://server01.consul:8200/v1/sys/mounts/gen
Code: 400. Errors:

* Unrecognized remote plugin message:

This usually means that the plugin is either invalid or simply
needs to be recompiled to support the latest protocol.

Answer 3 · 2019-09-27T15:13:30.000Z

[vagrant@server01 ~]$ /usr/local/bin/vault secrets disable gcp/
Success! Disabled the secrets engine (if it existed) at: gcp/

Answer 4 · 2019-09-27T16:06:45.000Z

Can you try Vault 1.2.3? I think I built against that version...

Answer 5 · 2019-09-27T16:19:27.000Z

Same error.

Answer 6 · 2019-09-27T17:01:31.000Z

I just tested and I'm unable to reproduce this on the released version.

$ vault secrets disable gen
Success! Disabled the secrets engine (if it existed) at: gen/```

Answer 7 · 2019-09-27T17:32:00.000Z

For clarity: vault 1.2.3 and vault-secrets-gen 0.0.4?

Answer 8 · 2019-09-27T19:22:54.000Z

I have to build against Vault v1.3.0-dev ('2b8aeb10cc859b5369781b7ad4a45fc774817a09').

But I just tested against 1.2.3 build:

$ vault -v
Vault v1.2.3

$ vault secrets disable gen
Success! Disabled the secrets engine (if it existed) at: gen/

Answer 9 · 2019-09-28T19:59:41.000Z

Works for me with Vault 1.2.2 and vault-secrets-gen 0.0.4?