Manager Exceptions aren't properly handled by API

Bug #1263116 reported by Sylvain Bauza
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Blazar
Fix Released
Medium
Sylvain Bauza

Bug Description

Climate (and other) Exceptions are thrown to the API thanks to AMQP but are not properly catched because the resulting exception is not inheriting from ClimateException, but rather Oslo's RemoteError

Changed in climate:
importance: Undecided → High
assignee: nobody → Sylvain Bauza (sylvain-bauza)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to climate (master)

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

Changed in climate:
status: New → In Progress
Dina Belova (dbelova)
Changed in climate:
importance: High → Medium
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to climate (master)

Reviewed: https://review.openstack.org/63445
Committed: https://git.openstack.org/cgit/stackforge/climate/commit/?id=b35935753b5998c2e0633f1708d71a29d166f276
Submitter: Jenkins
Branch: master

commit b35935753b5998c2e0633f1708d71a29d166f276
Author: Sylvain Bauza <email address hidden>
Date: Fri Dec 20 17:17:16 2013 +0100

    Fix Manager exceptions rendering for end-users

    Manager Exceptions were not properly catched by API, so consequently
    placed them all in one global Manager exceptions file and parsing
    it for knowing if it's a Climate Exception

    Also partially fixes #1257204

    Closes-Bug: #1263116

    Partial-Bug: #1257204

    Change-Id: Ic488ceab6ea6bed1ae2b1528e08810edfffde5be
    Implements: bp:

Changed in climate:
status: In Progress → Fix Committed
Dina Belova (dbelova)
Changed in climate:
milestone: none → 0.1.0
status: Fix Committed → Fix Released
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.