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
Reproduced this on consul-template master using Vault's AWS secret backend with a lease period of 2 minutes and the following test template that read accesskeys and stored them in a file
This causes consul template to constantly calling vault to renew the secret instead of every ~30 seconds (because the code uses 1/3 the lease period as the renew interval).
I found the root cause, will have a PR for it shortly.
I think I'm running into this issue. We have a dynamic MySQL secret backend setup at database/creds/wordpress_agent. Here's the relevant part of our Consul template:
{{ with secret "database/creds/wordpress_agent" }}
define('DB_USER', '{{ .Data.username }}');
define('DB_PASSWORD', '{{ .Data.password }}');
{{ end }}
And here's how we call consul-template in our container:
The template is rendered as expected, be still results in these log messages being output repeatedly and constantly:
[WARN] vault.read(database/creds/wordpress_agent): failed to renew: Error making API request.
URL: PUT http://vault.service.consul:8200/v1/sys/leases/renew
Code: 403. Errors:
* permission denied
The lease duration is set to 12h and it renewable:
Reproduced this on consul-template master using Vault's AWS secret backend with a lease period of 2 minutes and the following test template that read accesskeys and stored them in a file
This causes consul template to constantly calling vault to renew the secret instead of every ~30 seconds (because the code uses 1/3 the lease period as the renew interval).
I found the root cause, will have a PR for it shortly.
Found this when investigating hashicorp/nomad#3197
The text was updated successfully, but these errors were encountered: