When canaries fail in a deployment with lesser count than its predecessor, the culled allocations are never restored #19643
Labels
hcc/jira
stage/accepted
Confirmed, and intend to work on. No timeline committment though.
theme/deployments
theme/scheduling
type/bug
I've encountered a situation (In Nomad 1.7.3.dev) where Nomad eagerly culls previous-version allocations when a new job version deployment calls for a lower count, even when there are canaries involved, and does not reinstate the culled allocations in the case that the new deployment fails.
Per #5033 (comment) (and internal discussion with the team), this seems like a bug.
Reproduction steps
count
down from 20 to 15Expected Result
Actual Result
Job file (if appropriate)
The text was updated successfully, but these errors were encountered: