You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix a bug where system jobs may fail to be placed on a node that
initially was not eligible for system job placement.
This changes causes the reschedule to re-evaluate the node if any
attribute used in feasibility checks changes.
Fixes#8448
Fix a bug where system jobs may fail to be placed on a node that
initially was not eligible for system job placement.
This changes causes the reschedule to re-evaluate the node if any
attribute used in feasibility checks changes.
Fixes#8448
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.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
If a node is initially ineligible for a system job, the node will not get scheduled an allocation when it becomes eligible for one.
The reason is that the node doesn't get re-evaluated unless the node update updates status in https://github.com/hashicorp/nomad/blob/v0.12.0/nomad/node_endpoint.go#L172-L185 .
Reproduction steps
nomad agent -dev
nomad job run ./example.nomad
- notice thatnomad job status example
reports no allocationsnomad node status -self
to report the driver as healthynomad job status example
doesn't report any allocation on the nodeA workaround is to force evaluation of the job or re-submit, and it will be scheduled on the node as expected.
Job file (if appropriate)
The text was updated successfully, but these errors were encountered: