-
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
Can't resolve ID of some jobs placed in another region #3679
Comments
@tantra35 Are both regions running 0.7.1? |
@dadgar Yes of course we upgrade all regions |
And this is independent of job name length, as we thinked before, because |
@tantra35 Can you do |
|
@tantra35 Can you also try this:
And to be clear the results from the other API are via querying through another regions servers? |
@dadgar I think you made a mistake in
So I allowed myself to modify payload:
For zabbixserver(not working)
For ldap(it's working)
|
@tantra35 Thanks for all the info, will really help debugging! In the mean time, I believe if you use |
@dadgar Sorry but no :-(
And as i can make conclusion when we try to make search by
|
@tantra35 What is the results of the search request if you do it directly to that regions servers |
@dadgar it that case all works as expected without any problems For examle from one of the servers in region
then on the same server
|
@dadgar I'm so sorry for what has misled you, in |
So valid way to got status for job now is |
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.7.1 (0b295d3)
If we made this cli call we can see all jobs placed in some region:
but if we want to see status of partucular job for some of them we got follow:
but for example nomad status of zabbixproxy work perfectly:
We see this in 0.6.3 too but thinks that this is GH-3203. But upgrade from 0.6.3 to 0.7.1 doens't solve problem.
The text was updated successfully, but these errors were encountered: