-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Empty response on /auth/token/renew-self #2749
Comments
What is the error printed in Vault's log? |
Sorry, it took me a while to reproduce the issue, because we had to downgrade meanwhile. The following stacktrace seems to be most relevant
there are quite a few of them and, as far as I can see, every request to
But they seem to be related to a missing permission in mysql and should not cause the behaviour above, I guess? |
What version of Vault is that stacktrace from? |
Same as above (we tried to upgrade again, after fixing other things):
|
I've got a patch you can try if you're interested. |
Thanks for the fast response! I am going to try your patch as soon as possible in a test environment. |
Cool -- see that PR above for it. |
I can confirm that #2755 fixes the problem. 🎉 |
Hi,
After we upgraded our Vault to v0.7.2 ('d28dd5a018294562dbc9a18c95554d52b5d12390'), we started to experience some issues.
consul-template
suddenly failed to renew its tokens:The problem persisted after a restart of both, vault and consul-template, so I tried to reproduce it using curl and, sadly, succeeded:
I would have expected either a renewed token or an error message instead of the empty reply. Most other features seem to continue working, consul-templates succeeds in fetching credentials during the initial period before it tries to renew the token.
Did I miss any relevant information? I did not see anything suspicious in the changelog.
The text was updated successfully, but these errors were encountered: