Sahara

Validation errors from jsonshema are not informative

Bug #1540809 reported by Andrey Pavlov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Sahara
Fix Released
Medium
Andrey Pavlov
Sahara mitaka-3 "m3"

Bug Description

Sometimes it's hard to understand which part of the request is not correct from validation errors.

Vitalii Gridnev (vgridnev)
Changed in sahara:
importance: Undecided → Medium
assignee: nobody → Andrey Pavlov (apavlov-n)
status: New → In Progress
status: In Progress → Triaged
milestone: none → mitaka-3
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to sahara (master)

Fix proposed to branch: master
Review: https://review.openstack.org/275112

Changed in sahara:
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to sahara (master)

Reviewed: https://review.openstack.org/275112
Committed: https://git.openstack.org/cgit/openstack/sahara/commit/?id=11e6439938e323c491011fe76d92f9ebc6de2f94
Submitter: Jenkins
Branch: master

commit 11e6439938e323c491011fe76d92f9ebc6de2f94
Author: Andrey Pavlov <email address hidden>
Date: Tue Feb 2 13:39:23 2016 +0300

    Adding more information to validation errors

    All jsonschema validation failures will be printed
    in one error message. Also this message will contain
    the name of the parameter which doesn't pass validation.

    Closes-bug: #1540809

    Change-Id: I7fa82d2e873326f8a061ea13394eb0831c638e21

Changed in sahara:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.