Open Stack

On 00:08 Wed 14 May     , Trump.Zhang wrote:
> Hi, all:
> 
>      I find a lot of methods in cinder.api.contrib.* return 202 code
> instead of 200, even when these methods only involve database operation,
> which are not async process. For example,
> cinder.api.contrib.types_extra_specs.\
> VolumeTypeExtraSpecsController:delete, cinder.api.contrib.volume_actions.\
> VolumeActionsController:_reserve, etc.
> 
>     From the HTTP/1.1 Status Code Definitions [1], 202 means "Accepted",
> i.e. the request has been accepted for processing, but the processing has
> not been completed.
> 
>     Are these response codes are returned by mistake?

If it's just a db operation, that sounds like a mistake. Unfortunately, we have
not spent time on dealing with versioned extensions to easily deal with this.

https://wiki.openstack.org/wiki/APIChangeGuidelines

>--
Mike Perez