Replacement allocations during canary deployments are placed in the wrong datacenter #17651
Labels
stage/accepted
Confirmed, and intend to work on. No timeline committment though.
theme/scheduling
type/bug
Nomad version
But it likely happens in previous versions as well.
Operating system and Environment details
N/A
Issue
When a job with canary deployments changes its
datacenters
and, during deployment, an allocation for the previous version fails, the replacement allocations are created in nodes for the newdatacenters
value instead of the original one.Reproduction steps
nomad agent -dev
and run the job below to create some extra clients.Nomad clients jobfile
Run sample job below. One of the allocations will keep failing.
Update the job's datacenter.
Run job again and monitor its allocations
Expected Result
The replacement allocation is created in the same node and in the same datacenter as it was originally.
Actual Result
The replacement allocation is created in the new datacenter.
Job file (if appropriate)
The text was updated successfully, but these errors were encountered: