Magnum

certificate sign with a non-existing cert throws HTTP 500 instead of HTTP 400

Bug #1543643 reported by Dimitry Ushakov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Magnum
Fix Released
Undecided
space

Bug Description

Currently, POST /certificates with an invalid/not defined cert throws HTTP 500 error (internal server error). Should be HTTP 400 (bad request)

space (fengzhr)
Changed in magnum:
assignee: nobody → space (fengzhr)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to magnum (master)

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

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

Reviewed: https://review.openstack.org/281044
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=d8cf838dd3d97d161972e98f3f94352579b8af70
Submitter: Jenkins
Branch: master

commit d8cf838dd3d97d161972e98f3f94352579b8af70
Author: space <email address hidden>
Date: Wed Feb 17 12:16:38 2016 +0800

    certificate sign with a non-existing cert should throw HTTP 400

    Add throw exception for the validate code of CSR. Then it
     will throw HTTP 400 when the CSR validation is not passed.

    Change-Id: I6603a2a243097687fef8666343b993c0a18946a9
    Closes-Bug: #1543643

Changed in magnum:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/magnum 2.0.0

This issue was fixed in the openstack/magnum 2.0.0 release.

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.