adding an image property differing only in case from a current property causes a 500

[Brian Rosmaita]

Observed in devstack with M-3.

The case in property names created with the v2 API is respected, that is, you can create a property with the name 'SomeProperty', and that's how it will appear in output from the v2 API. If you then try to add a property 'someproperty' (or any other differing case) with either the v2 or v1 API, the result is a 500.

We've discussed this on the ML and in IRC, the result should be a 4xx for an attempt to create a duplicate image property.

[OpenStack Infra (hudson-openstack)]

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

[Brian Rosmaita (brian-rosmaita)]

There's not really a DocImpact here, but I will add some stuff to the docs to clarify what Glance means by a "duplicate property name", and to remind consumers of image records that they should normalize property names before using them programmatically.

[OpenStack Infra (hudson-openstack)]

Change abandoned by Nikhil Komawar (<email address hidden>) on branch: master
Review: https://review.openstack.org/291198
Reason: I see no movement on this patch. Please reopen as/when you find appropriate.