OpenStack Compute (Nova)

OS API: Metadata key thats length exceeds system limit throws incorrect error

Reported by Daryl Walleck on 2012-01-17
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Low
Russell Bryant

Bug Description

If the length of a metadata key exceeds the compute provider limit, the API returns a 500 as opposed to the 413 stated in the spec. This issue can be reproduced with test test_server_create_metadata_key_too_long in test_server_metadata.py from Tempest.

Brian Waldon (bcwaldon) on 2012-01-27
Changed in nova:
status: New → Triaged
importance: Undecided → Low
Russell Bryant (russellb) wrote :

Can you check and see if you can still reproduce this? I tried to write a unit test for this (attached) and got the expected behavior.

Changed in nova:
status: Triaged → Incomplete
Russell Bryant (russellb) wrote :
Changed in nova:
assignee: nobody → Russell Bryant (russellb)

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

Changed in nova:
status: Incomplete → In Progress

Reviewed: https://review.openstack.org/4748
Committed: http://github.com/openstack/nova/commit/5671515f693c90b68f784748843a07214880a1f8
Submitter: Jenkins
Branch: master

commit 5671515f693c90b68f784748843a07214880a1f8
Author: Russell Bryant <email address hidden>
Date: Thu Feb 23 15:51:48 2012 -0500

    Test creating a server with metadata key too long.

    Related to bug 917484.

    This bug reported that the OpenStack API returned the wrong type of
    error when creating an instance with a metadata key that was too long.
    I added this unit test to try it out and it appears to work as expected,
    so might as well just keep the test around.

    Change-Id: Ie4bcf81741a268fd8319e1ecaad5639ad8c9b6f7

Changed in nova:
status: In Progress → Fix Committed
Thierry Carrez (ttx) on 2012-03-20
Changed in nova:
milestone: none → essex-rc1
status: Fix Committed → Fix Released
Thierry Carrez (ttx) on 2012-04-05
Changed in nova:
milestone: essex-rc1 → 2012.1
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers