Cryptic error message when using bad GCE credentials
Bug #1622581 reported by
Martin Hilton
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Expired
|
Medium
|
Unassigned | ||
Bug Description
I tried to bootstrap a GCE controller using what turned out to be bad credentials. The error message I got was 'ERROR missing "type"'. This was less helpful than it might be in working out what was going wrong.
| Changed in juju-core: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| no longer affects: | juju-core |
| Changed in juju: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| tags: | added: usability |
Revision history for this message
| Anastasia (anastasia-macmood) wrote | #1 |
| Changed in juju: | |
| status: | Triaged → Incomplete |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #2 |
| Changed in juju: | |
| status: | Incomplete → Expired |
To post a comment you must log in.
Juju tries to be helpful and tends to provide error messages that will give users guidance on what went wrong and how to correct the situation.
Could you please share an example of what specifically was wrong in your case? We would like to ensure that a message is focused and dedicated to an individual scenario and avoids ambiguity.