Cinder

update volume's metadata returns 500 error

Bug #1598007 reported by wangxiyuan on 2016-07-01

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	Cinder	Fix Released	Low	wangxiyuan	Cinder newton-2 "n2"

Bug Description

The volume update API also allow users to update the volume'metadata. But cinder doesn't check the length limit. It'will raise 500 error if the metadata is longer than 255. We should check it and raise 413 at the api layer.

See original description

wangxiyuan (wangxiyuan) on 2016-07-01

Changed in cinder:
assignee:	nobody → wangxiyuan (wangxiyuan)
description:	updated

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2016-07-01: Fix proposed to cinder (master)

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

Changed in cinder:
status:	New → In Progress

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2016-07-07: Fix merged to cinder (master)

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

commit f6aec5bb96424668ac8ff9ae48899dc5354ea26a
Author: wangxiyuan <email address hidden>
Date: Fri Jul 1 16:32:38 2016 +0800

check the validity of metadata when update volume

    The volume update API also allow users to update the volume'metadata.
    But cinder doesn't check the length limit. It'will raise 500 error
    if the metadata is longer than 255. We should check it and raise
    413 at the api layer to keep the same with the volume metadata
    update API.

Change-Id: I3928ffff9aab6a8071d0641fa6b40b10b1f6bc10
Closes-bug: #1598007