-
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
Nomad status reports "placement failure" even when job is running ok #2124
Comments
If you rename the job and try to |
No, I guess it has something to do with this loop https://github.com/hashicorp/nomad/blob/master/command/status.go#L267 |
I added evaluations to the client log. As you can see, the most recent evaluation 55f4cfd3 was successfull and job is running ok. |
Hey this is a known bug. It is only a UX issue and won't actually impact your job. Still an issue tho! |
This PR causes blocked evaluations to be cancelled if there is a subsequent successful evaluation for the job. This fixes UX problems showing failed placements when there are not any in reality and makes GC possible for these jobs in certain cases. Fixes #2124
This PR causes blocked evaluations to be cancelled if there is a subsequent successful evaluation for the job. This fixes UX problems showing failed placements when there are not any in reality and makes GC possible for these jobs in certain cases. Fixes #2124
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 v0.5.1
First, I tried do deploy a job with wrong datacenter "nomad-dc1". Nomad gave me Placement Failure as expected.
Then I redeployed the same job, but now with correct datacenter "production".
Job was successfully launched, but
nomad status
still reports Placement Failure:The text was updated successfully, but these errors were encountered: