Exceeding compute provider metadata limit on create causes a 500 instead of a 413

Bug #885986 reported by Daryl Walleck
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Fix Released
Low
Alex Meade

Bug Description

If I try to create a server with more metadata items than the defined limit, a 500 server error message is returned as opposed to a 413 as the spec states.

Thierry Carrez (ttx)
Changed in nova:
importance: Undecided → Low
status: New → Confirmed
Alex Meade (alex-meade)
Changed in nova:
assignee: nobody → Alex Meade (alex-meade)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to nova (master)

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

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

Reviewed: https://review.openstack.org/3044
Committed: http://github.com/openstack/nova/commit/9c1f5d49d7d2783054d1e01361298cddafeeec78
Submitter: Jenkins
Branch: master

commit 9c1f5d49d7d2783054d1e01361298cddafeeec78
Author: Alex Meade <email address hidden>
Date: Fri Jan 13 21:27:21 2012 +0000

    have all quota errors return an http 413

    Fixes bug 885986

    Change-Id: I13a5f600c643c4ce80d638cac98c1c9b999630b2

Changed in nova:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in nova:
milestone: none → essex-3
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in nova:
milestone: essex-3 → 2012.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.