mirror of
https://github.com/kemko/nomad.git
synced 2026-01-01 16:05:42 +03:00
82f0f00a83
node-update triggers should never trigger sysbatch allocations, these should only ever be create by periodic-job or job-register. An example scenario is: an allocation spawned by a sysbatch periodic job is running on a node, the allocation gets stopped, GC runs, the node becomes ineligible and eligible again, all within the parent sysbatch job period window. If this happens, node-update will trigger the system scheduler and prematurely start an allocation. This is not a desired behavior, and in fact a bug.
4 lines
92 B
Plaintext
4 lines
92 B
Plaintext
```release-note:bug
|
|
node: Fixed bug where sysbatch allocations were started prematurely
|
|
```
|