Die/warn of constraints which exceed available resources
Bug #1241733 reported by
Ryan Finnie
This bug report is a duplicate of:
Bug #1237163: juju deploys wrong machine when no machine matching constraints is available.
Edit
Remove
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
New
|
Undecided
|
Unassigned |
Bug Description
On an Openstack provider, I did a deploy with "--constraints mem=32G", but in our environment, the available flavors only had a maximum of 16GB. The unit created was instead created with a 1GB memory flavor, without any sort of warning or notification.
Constraints should be a minimum bound (constrained to be the minimum above the requested constraints). Not being able to satisfy the minimum constraint should produce an error, or at the very least a warning plus selecting the maximum flavor closest to being able to satisfy the constraints.
To post a comment you must log in.
There is a similar bug about cores=SOME_ IMPOSSIBLE_ NUMBER, i cannot find it at the moment