-
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
JSON job with ParentID set does not run #10422
Comments
ParentID is an internal field that Nomad sets for dispatched or parameterized jobs. Job submitters should not be able to set it directly, as that messes up children tracking. Fixes #10422 . It specifically stops the scheduler from honoring the ParentID. The reason failure and why the scheduler didn't schedule that job once it was created is very interesting and requires follow up with a more technical issue.
I can confirm that job deployment works after removing ParentID property.. |
ParentID is an internal field that Nomad sets for dispatched or parameterized jobs. Job submitters should not be able to set it directly, as that messes up children tracking. Fixes #10422 . It specifically stops the scheduler from honoring the ParentID. The reason failure and why the scheduler didn't schedule that job once it was created is very interesting and requires follow up with a more technical issue.
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. |
Issue
When submitting a job with a ParentID set to a non-empty value, versions of Nomad > v.0.12.1 do not create an evaluation and consequently the job does not run. This is a change in behavior from Nomad v0.12.0 and earlier. Removing the ParentID from the job causes the job to work as expected.
Reproduction steps
Expected Result (pre-v0.12.1)
Run a Nomad v0.12.0 dev agent with the included configuration
Submit the job to the agent
Server logs around the submit event:
Check the status of the job
lightningCollector-lightningCollector
. Note that it has been evaluated and made a blocked eval based on the constaint.Fetch the evaluation via the API
Actual Result (v0.12.1 and beyond)
Run a Nomad v0.12.1 dev agent with the included configuration
Submit the job to the agent
Server logs around the submit event:
Check the status of the job
lightningCollector-lightningCollector
. Note that it doesn't seem to have been evaluated because there isn't a blocked eval based on the constaint.Fetch the evaluation via the API
Job file (if appropriate)
Click for Job file
The text was updated successfully, but these errors were encountered: