'juju deploy" errors are not very polished
Bug #1661937 reported by
John A Meinel
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Expired
|
Medium
|
Unassigned | ||
Bug Description
When looking over the deploy tests, I don't think anyone really sat down and decided that these were really useful and helpful errors. Some things were obviously thought about (giving multiple errors when there is more than one thing wrong). Some others are not as nice:
examples:
cannot deploy bundle: cannot add unit for application "django": adding new machine to host unit "django/0": cannot assign unit "django/0" to machine 0: series does not match
cannot deploy bundle: cannot deploy application "wp": cannot add application "wp": unknown space "public" not valid
| tags: | added: usability |
| Changed in juju: | |
| milestone: | 2.2-beta1 → none |
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.