[UX] Better error message when "agent binars not available"
Bug #1989213 reported by
Erik Lönroth
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Triaged
|
Wishlist
|
Unassigned | ||
Bug Description
If a user tried to deploy --series "centos7" (or whatever).
The error message is just saying "no agent binaries available".
It does not let a user know if this is a fatal situation, or, if the user in fact can remedy the situation.
I would like to have the error message be letting me know WHAT can I do about it. Like "do this or that" to fix it.
See the image about the situation.
Letting a user know about likely actions to take to recover from an error is generally something I would ask for with juju. Its very common this kind of situations, e.g. "ERROR - No mor information.
Revision history for this message
| Erik Lönroth (erik-lonroth) wrote | #1 |
| Changed in juju: | |
| assignee: | nobody → Evanson Mwangi (mr-parish) |
| milestone: | none → 2.9-next |
| importance: | Undecided → Medium |
| Changed in juju: | |
| status: | New → Triaged |
| importance: | Medium → Wishlist |
| status: | Triaged → New |
| Changed in juju: | |
| status: | New → Triaged |
| Changed in juju: | |
| assignee: | Evanson Mwangi (mr-parish) → nobody |
| milestone: | 2.9-next → 3.2-beta1 |
| Changed in juju: | |
| milestone: | 3.2-beta1 → 3.2-rc1 |
| Changed in juju: | |
| milestone: | 3.2-rc1 → 3.2.0 |
| Changed in juju: | |
| milestone: | 3.2.0 → 3.2.1 |
| Changed in juju: | |
| milestone: | 3.2.1 → 3.2.2 |
| Changed in juju: | |
| milestone: | 3.2.2 → 3.2.3 |
| Changed in juju: | |
| milestone: | 3.2.3 → 3.2.4 |
| Changed in juju: | |
| milestone: | 3.2.4 → 3.2.5 |
| tags: | added: community-feedback usability |
| Changed in juju: | |
| milestone: | 3.2.5 → none |
To post a comment you must log in.
