Bad parameter exception

Bug #1382468 reported by Ladislav Smola on 2014-10-17
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
python-tuskarclient
Medium
Petr Blaho
tuskar
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.

Petr Blaho (pblaho) on 2014-10-17
Changed in tuskar:
assignee: nobody → Petr Blaho (pblaho)
status: New → Triaged
Petr Blaho (pblaho) on 2014-10-23
affects: tuskar → python-tuskarclient
Changed in tuskar:
status: New → Triaged
assignee: nobody → Petr Blaho (pblaho)
Clint Byrum (clint-fewbar) wrote :

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.

Changed in python-tuskarclient:
importance: Undecided → Medium
Changed in tuskar:
importance: Undecided → Medium
Dougal Matthews (d0ugal) on 2016-01-27
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.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers