Cinder consistency group returning generic error message

Bug #1610295 reported by David Rosales
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cinder
Fix Released
Medium
haobing1

Bug Description

When trying to create a consistency group with the quota reached already, the error raised to the user is the generic "ERROR: The server has either erred or is incapable of performing the requested operation. (HTTP 500)" message. The true reason can be found in the logs.

OverQuota: Quota exceeded for resources: ['consistencygroups']

My feeling is that this error message should be returned to the user with a 400 error code.

Changed in cinder:
importance: Undecided → Medium
haobing1 (haobing1)
Changed in cinder:
assignee: nobody → haobing1 (haobing1)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to cinder (master)

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

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

Reviewed: https://review.openstack.org/408365
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=2655e8bba9279dec7c4fbbea28e6a011272794e2
Submitter: Jenkins
Branch: master

commit 2655e8bba9279dec7c4fbbea28e6a011272794e2
Author: haobing1 <email address hidden>
Date: Wed Dec 7 21:50:18 2016 +0800

    Cinder consistency group returning generic error message

    When trying to create a consistency group with the quota reached
    already, the error raised to the user is the generic "ERROR: The
    server has either erred or is incapable of performing the requested
    operation. (HTTP 500)" message.
    This patch will make the error message return to the user with
    a 413 error code. Such as "ERROR: GroupLimitExceeded: Maximum number
    of groups allowed (10) exceeded'.(HTTP 413)"

    Change-Id: I0dd86dbc84d3dc75568c39aca8150c8fa12c4811
    Closes-Bug: #1610295

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

This issue was fixed in the openstack/cinder 10.0.0.0b3 development milestone.

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.