unused machine assignment ignores constraints
Bug #1161919 reported by
William Reade
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Won't Fix
|
Low
|
Unassigned |
Bug Description
When using a provider with the "unused" assignment policy (of which none currently exist), units may be assigned to machines that do not fit the constraints that should be applied to the unit.
When we use that policy, we should ensure that the unit's constraints are respected, such that units are only assigned to (1) provisioned machines whose instances match the unit's constraints or (2) unprovisioned machines, that can thus take new constraints from the unit (*before* they are provisioned by an eager provisioner).
Changed in juju-core: | |
importance: | Undecided → Medium |
status: | New → Triaged |
Changed in juju-core: | |
assignee: | nobody → Nate Finch (natefinch) |
Changed in juju-core: | |
importance: | Medium → Low |
tags: | added: constraints |
Changed in juju-core: | |
assignee: | Nate Finch (natefinch) → nobody |
Changed in juju-core: | |
status: | Triaged → Won't Fix |
To post a comment you must log in.