create container on machine without space should be forbidden
Bug #1650254 reported by
John A Meinel
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Expired
|
High
|
Unassigned | ||
Bug Description
somewhat related to bug #1650253.
If you try to 'juju add-machine lxd:N --constraints spaces=X' (or deploy foo --to lxd:N --bind X), even if we know about space X, but it isn't on machine N, we should reject the provisioning request as early as possible. Preferably we reject the 'add-machine' request, but maybe we can't detect it easily until actual provisioning.
But the error message for doing such a thing should be clear.
Revision history for this message
| Canonical Juju QA Bot (juju-qa-bot) wrote | #1 |
| Changed in juju: | |
| status: | Triaged → Expired |
| tags: | added: expirebugs-bot |
To post a comment you must log in.
This bug has not been updated in 5 years, so we're marking it Expired. If you believe this is incorrect, please update the status.