Unhelpful error message when no nodes are available with maas provider
Bug #980855 reported by
Francis J. Lacoste
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| pyjuju |
Fix Released
|
Medium
|
Julian Edwards | ||
Bug Description
Using the maas provider, I ran
juju bootstrap
and got:
Unexpected Error interacting with provider: 409 CONFLICT
The reason is that there were no nodes available in the MAAS.
The error message is completely unhelpful in making the user understand what is the source of the error.
We should tell them that it's failing because no nodes are available to fullfill their requests.
Related branches
lp:~julian-edwards/pyjuju/show-errors-when-acquiring-node
- Kapil Thangavelu (community): Approve
- William Reade (community): Approve
-
Diff: 127 lines (+33/-11)4 files modifiedjuju/providers/maas/maas.py (+17/-2)
juju/providers/maas/tests/test_launch.py (+4/-6)
juju/providers/maas/tests/test_maas.py (+10/-1)
juju/providers/maas/tests/testing.py (+2/-2)
| Changed in juju: | |
| milestone: | none → galapagos |
| status: | New → Confirmed |
| importance: | Undecided → Medium |
Revision history for this message
| Jeroen T. Vermeulen (jtv) wrote | #1 |
| Changed in juju: | |
| assignee: | nobody → Julian Edwards (julian-edwards) |
| status: | Confirmed → In Progress |
| Changed in juju: | |
| status: | In Progress → Fix Released |
To post a comment you must log in.
The response that Juju gets back from the MAAS server is indeed a 409: Conflict, but the response body also contains a somewhat helpful message (currently “No matching node is available”). It might help just to display the response's contents as part of the error.