-
Notifications
You must be signed in to change notification settings - Fork 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
Unable to revert a Nomad job with Vault policies when allow_unauthenticated is set to false #4555
Comments
It is worth looking at whether this issue is also related to #4226 |
I don't believe they are related. My issue seems to occur for an API call against a Nomad master to the revert the job to a previous version. The issue #4226 is related to restarting the Nomad client service. |
Any news about this issue? I have the same problem. Nomad v8.4 with VAULT_TOKEN exported. |
thanks for the report, targeting this for 0.9.1 |
Thank you |
Hey there Since this issue hasn't had any activity in a while - we're going to automatically close it in 30 days. If you're still seeing this issue with the latest version of Nomad, please respond here and we'll keep this open and take another look at this. Thanks! |
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues. |
Nomad version
Nomad v0.8.4
Operating system and Environment details
CentOS 7.5
Issue
Unable to revert to a previous revision of a job when
allow_unauthenticated
is set to false on the nomad server. We can create the job and the validation works. However when attempting to do a revert I get a 500 error that the Vault token is missing. This is a similar error I would receive if I did not provide a vault token when attempting a run.Reproduction steps
Job file (if appropriate)
The text was updated successfully, but these errors were encountered: