mirror of
https://github.com/kemko/nomad.git
synced 2026-01-01 16:05:42 +03:00
When a disconnected alloc reconnects, the follow-up evaluation is left pending and the followup eval ID field isn't cleared. If the allocation later fails, the followup eval ID prevents the server from creating a new eval for that event. Update the state store so that updates from the client clear the followup eval ID if the allocation is reconnecting, and mark the eval as canceled. Update the FSM to remove those evals from the eval broker's delay heap. Fixes: https://github.com/hashicorp/nomad/issues/12809 Fixes: https://hashicorp.atlassian.net/browse/NMD-302
4 lines
110 B
Plaintext
4 lines
110 B
Plaintext
```release-note:bug
|
|
disconnect: Fixed a bug where pending evals for reconnected allocs were not cancelled
|
|
```
|