-
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
Periodic jobs are never marked as complete in the job summary list #8903
Comments
Hey folks - any updates on this? Experiencing this on Nomad 1.0.3. All of our batch jobs show thousands of pending jobs, equal to the number of dead jobs. Thanks! |
Hi @evandam! I have a suspicion this is fixed by #9768 which will land in 1.0.4. That was a fix for #8692 but looking at the commit ref you posted I know that was discussed as part of the cause there. I'll try to reproduce and verify that patch; will probably be early next week and we'll figure out what to do if anything from there. |
Using the repro above:
Going to close this and mark it for release in 1.0.4 |
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.12.1+
Operating system and Environment details
Reproduced on MacOS and Linux
Issue
After running a periodic job, the spawned jobs never transition to a complete state, even if they run successfully. They will always be marked as
pending
in the job summary list:But each job, alloc and eval are completed succesfully:
The issue started in the commit 97c69ee. Building from its parent doesn't trigger this problem. This also only happens with periodic jobs. Regular batch and dispatched jobs are not affected.
Reproduction steps
nomad status batch
The list show all jobs as pending.
Job file (if appropriate)
The text was updated successfully, but these errors were encountered: