Volume type extra specs delete always returns 202 status code

[Rohan]

Branch : master

Api : DELETE http://<ip>:8776/v1/<tenant_id>/types/<vol_type_id>/extra_specs/<spec_name>

Issue : The above api http call always returns http status code of 202 , even if the <spec_name> does not exist, in which case it should return http status code 404.

[John Griffith (john-griffith)]

Most of the extensions just always return the 202 as you've pointed out. We could probably use some clean-up and better reporting here but I think this will be a V2 API task as opposed to changing all of the behaviors in V1.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/31044
Committed: http://github.com/openstack/cinder/commit/de84fd7b1539893bf48ed8b36db1bfdeaf05d7a9
Submitter: Jenkins
Branch: master

commit de84fd7b1539893bf48ed8b36db1bfdeaf05d7a9
Author: Cian O'Driscoll <email address hidden>
Date: Thu May 30 13:00:54 2013 +0000

    Return 404 from delete of extra spec if not found

    API service now returns a 404 if the volume type that the
    user is trying to delete doesn't exist.

    Fixed Bug 1090306.

    Change-Id: I3c1d4fdac1c2492f532ab4dbfd5c7aaf0ffa6fa4