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
If I shutdown client nodes, jobs that were in the dead state switch back to the pending state.
Reproduction Steps
Configure a 3 node server cluster. Bring up a single client node. Submit a single batch job with a task count of 1 using the Docker driver. Let the job run to completion. If you run a nomad status the jobs will be in the dead state. Shutdown the client node. The job switches back to the pending state.
Note: I did not test this with other job types or drivers. May be specific to this combination... or may not be.
Nomad Server Config (other 2 are identical except for advertise IP)
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.
Nomad Version
nomad version
Nomad v0.3.2
Operating System and Environment Details
CentOS7 3.10.0-327.13.1.el7.x86_64
Issue
If I shutdown client nodes, jobs that were in the dead state switch back to the pending state.
Reproduction Steps
Configure a 3 node server cluster. Bring up a single client node. Submit a single batch job with a task count of 1 using the Docker driver. Let the job run to completion. If you run a nomad status the jobs will be in the dead state. Shutdown the client node. The job switches back to the pending state.
Note: I did not test this with other job types or drivers. May be specific to this combination... or may not be.
Nomad Server Config (other 2 are identical except for advertise IP)
Nomad Client Config
Job File
The text was updated successfully, but these errors were encountered: