-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Vault client not active #2143
Comments
Please upgrade to 0.5.2 and see if this is still a problem. PR #2050 likely fixed this and is merged in 0.5.1 and on. |
It seems to be working now but there is this odd message found in server logs when I run the job:
I can |
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.5.0
Operating system and Environment details
Ubuntu 16.04 EC2 m3.xlarge
Issue
When I run a job that requires Vault integration token create fails:
Looking at the source code I think maybe the Vault client is only being set to active on the leader node? It appears that the job is being processed on stg-clustermgr-master08 which is not the leader node.
Reproduction steps
nomad run asky-log
watch logs with
journalctl -f -n100 -u nomad.service
on stg-clustermgr-master08Job file (if appropriate)
The text was updated successfully, but these errors were encountered: