Missing error handle for quota

Bug #1116137 reported by Alex Xu
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Fix Released
Medium
Alex Xu

Bug Description

Quota should handle error by 'quantum.api.resource.Resource' same as core resource

Alex Xu (xuhj)
Changed in quantum:
assignee: nobody → Alex Xu (xuhj)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to quantum (master)

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

Changed in quantum:
status: New → In Progress
dan wendlandt (danwent)
Changed in quantum:
milestone: none → grizzly-rc1
importance: Undecided → Medium
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to quantum (master)

Reviewed: https://review.openstack.org/21197
Committed: http://github.com/openstack/quantum/commit/987b1a35cdb3631ab759b5ee6b63ad6ecb8e1753
Submitter: Jenkins
Branch: master

commit 987b1a35cdb3631ab759b5ee6b63ad6ecb8e1753
Author: He Jie Xu <email address hidden>
Date: Tue Feb 5 19:05:53 2013 +0800

    Wrap quota controller with resource.Resource

    Fixes bug 1116137

    Currently the format of error message returned by quota extension was
    different with quantum other resource. Other resource will return as
    json(eg, '{"QuantumError": "error message"}'). But quota extension only
    return messages without any format.
    'quantum.api.v2.resource.Resource' provider error messages processing.
    So wrap quota controller with it.

    By the way, fix some small stuff:
    * Use specific exception 'QuotaTenantNotFound' instead of generic exception.
    * Correct error message.
    * Use attribute mapping checking the request body.

    Change-Id: I71261198aa79e9ed8e0ae672de32552abdbf45c1

Changed in quantum:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in quantum:
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in quantum:
milestone: grizzly-rc1 → 2013.1
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.