-
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
Periodic jobs duplicate pending on children job summary #8692
Comments
Hi @Brinuz. Thanks for providing an easy reproduction on this. We'll take a look |
Hey @jorgemarey this is related to the changes in #8435, The team is discussing a few approaches to fix the issue. The nomad/nomad/state/state_store.go Lines 4425 to 4432 in 9c3ce6b
I am working on further debugging and testing and will hopefully have another update soon |
Possibly related: #9775 |
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.3
(I could replicate it in all versions after v0.12.1, but not on v0.12.0)
Operating system and Environment details
OSX v10.15.5
I'm simply running the agent in
-dev
to reproduce it.Issue
This seems to happen only on periodic jobs.
After a job is normally run or forced, the job children summary ends up with
1 pending
and1 done
.Seems like it initially increases the pending count to 2 and eventually changes the count to
1 pending
and1 running
, and eventually to1 pending
and1 done
.Keep in mind: I'm only running the job once and in fact, only one job is launched.
If I let it run again, the same happens, except I will end up with 2 pending and 2 done (forever).
Of course, I would expect to see it going from
1 pending
to1 running
and ending up in1 dead
and on and on.For each new job launch, there's always a new extra
pending
in the summary.Reproduction steps
nomad agent -dev
nomad job run test.nomad
which schedules the job to eventually run.nomad job periodic force test
nomad job status test
to check the above output (or similar) withX pending
andX done
.Job file (if appropriate)
Job file from the example above (
test.nomad
):Nomad agent logs from start to finish.
The text was updated successfully, but these errors were encountered: