| 2016-03-07 22:35:40 |
Brian Rosmaita |
description |
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'. If you then try to add a property 'someproperty' 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 400 for an attempt to create a duplicate image property. |
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 400 for an attempt to create a duplicate image property. |
|
| 2016-03-10 13:53:07 |
Brian Rosmaita |
description |
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 400 for an attempt to create a duplicate image property. |
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. |
|
