Kuryr doesn't return the error response with the error message

Bug #1503518 reported by Taku Fukushima
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fix Committed
Taku Fukushima

Bug Description

KuryrException is not extending Exception appropriately and Kuryr returns the error response with the empty message.

Changed in kuryr:
assignee: nobody → Taku Fukushima (tfukushima)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to kuryr (master)

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

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

Reviewed: https://review.openstack.org/231843
Committed: https://git.openstack.org/cgit/openstack/kuryr/commit/?id=5b9024ea424abe6494f6e26f72f7838c189eea3c
Submitter: Jenkins
Branch: master

commit 5b9024ea424abe6494f6e26f72f7838c189eea3c
Author: Taku Fukushima <email address hidden>
Date: Wed Oct 7 13:18:09 2015 +0900

    Modify KuryrException extend Exception appropriately

    This patch modifies KuryrException call the initializer of the super
    class. This fixes Kuryr not to return the empty error response.

    Change-Id: I728a24df6f20a81090c98aac46be22f3d27cd884
    Signed-off-by: Taku Fukushima <email address hidden>
    Closes-Bug: #1503518

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

Other bug subscribers

Remote bug watches

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