Bad parameter exception
Bug #1382468 reported by
Ladislav Smola
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| python-tuskarclient |
Won't Fix
|
Medium
|
Petr Blaho | ||
| tuskar |
Won't Fix
|
Medium
|
Petr Blaho | ||
Bug Description
When we update parameters in a Plan and we provide non-existent paramter, it will throw generic 500
When we update multiple parameters at once e.g. from CLI, it's very hard to debug which one was wrong.
It should LOG.error with parameter name and probably return verbose error to API too.
| Changed in tuskar: | |
| assignee: | nobody → Petr Blaho (pblaho) |
| status: | New → Triaged |
| affects: | tuskar → python-tuskarclient |
| Changed in tuskar: | |
| status: | New → Triaged |
| assignee: | nobody → Petr Blaho (pblaho) |
Revision history for this message
| Clint Byrum (clint-fewbar) wrote | #1 |
| Changed in python-tuskarclient: | |
| importance: | Undecided → Medium |
| Changed in tuskar: | |
| importance: | Undecided → Medium |
| Changed in python-tuskarclient: | |
| status: | Triaged → Won't Fix |
| Changed in tuskar: | |
| status: | Triaged → Won't Fix |
To post a comment you must log in.
Petr if you're going to set things to "Triaged" that implies you know the importance. Please make comments to that effect so we know what the priority is.