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
Periodic snapshots and saving state during Nomad client process shutdown save incorrect allocation state.
Reproduction steps
Run a simple job like the one listed below. Stop the job, then shutdown the Nomad process. Run nomad operator client-state /path/to/statestore | jq | grep "ClientStatus" and see the result is "running" even though the job was completed.
Optionally throw a log in the allocRunner's PersistState method printing out the allocs ClientStatus and see that it is incorrect. (It gets persisted as pending roughly ~30 seconds after being marked healthy)
Nomad version
1.9.3
Operating system and Environment details
Ubuntu 24.04.1
Issue
Periodic snapshots and saving state during Nomad client process shutdown save incorrect allocation state.
Reproduction steps
Run a simple job like the one listed below. Stop the job, then shutdown the Nomad process. Run
nomad operator client-state /path/to/statestore | jq | grep "ClientStatus"
and see the result is "running" even though the job was completed.Optionally throw a log in the allocRunner's
PersistState
method printing out the allocs ClientStatus and see that it is incorrect. (It gets persisted aspending
roughly ~30 seconds after being marked healthy)Expected Result
The
ClientStatus
should becompleted
Actual Result
The
ClientStatus
showsrunning
Job file (if appropriate)
Nomad Server logs (if appropriate)
N/A
Nomad Client logs (if appropriate)
Output of
nomad job status
Logs:
The text was updated successfully, but these errors were encountered: