Few API's should return 400 for non-existing parameters
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Invalid
|
Wishlist
|
Unassigned |
Bug Description
If you pass non-existing parameters in body to the volume API's, then it returns 404 HTTPNotFound error.
According to api guidelines [1] it should return 400 HTTPBadRequest.
[1] https:/
API's having incorrect return status code:
1.cinder create :
If you pass following non-existing parameters to volume create API,it returns 404 instead of 400:
a.consistency group id
b.source volume id
c.source replica id
d.snapshot id
3.cinder rename:
If you pass following non-existing parameters to volume rename API,it returns 404 instead of 400:
a.Volume ID
3.cinder snapshot-create:
If you pass following non-existing parameters to volume snapshot-create API,it returns 404 instead of 400:
a.Volume ID
4.cinder snapshot-delete:
If you pass following non-existing parameters to volume snapshot-delete API,it returns 404 instead of 400:
a.Volume ID
5.cinder snapshot-manage:
If you pass following non-existing parameters to volume snapshot-manage API,it returns 404 instead of 400:
a.Volume ID
6.cinder snapshot-rename:
If you pass following non-existing parameters to volume snapshot-rename API,it returns 404 instead of 400:
a.Volume ID
Changed in cinder: | |
assignee: | nobody → Pranali Khatode (pranali.khatode) |
Changed in cinder: | |
importance: | Undecided → Wishlist |
Fix proposed to branch: master /review. openstack. org/401941
Review: https:/