Normal response code of addSecurityGroup is wrong

Bug #1737338 reported by hongbin
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Invalid
Wishlist
Unassigned

Bug Description

Description
===========
According to nova's api-ref [1], the normal response code of addSecurityGroup is 202. However, according to OpenStack API guideline [2] , 202 is for "Asynchronous resource creation" but the addSecurityGroup action doesn't seem to be async. I think 200 is more appropriate in this case.

[1] https://developer.openstack.org/api-ref/compute/#add-security-group-to-a-server-addsecuritygroup-action
[2] http://specs.openstack.org/openstack/api-wg/guidelines/http.html#xx-success-codes

Tags: api
hongbin (hongbin034)
description: updated
tags: added: api
Revision history for this message
jichenjc (jichenjc) wrote :

guess we can modify all this kind of 20x return code in one patch with microversion bump... (if you search in the code, there are more like this)

Changed in nova:
status: New → Confirmed
importance: Undecided → Wishlist
Revision history for this message
Deepak Mourya (mourya007) wrote :
Revision history for this message
Ghanshyam Mann (ghanshyammann) wrote :

Yea, there are lot of other place where API status code are not consistent and as per guidelines. As jichenjc mentioned this will be API change and need microversion bump to maintain the backward compatibility.

And as per Nova process, every API change needs spec, so please write spec for this for further discussion.

Changed in nova:
status: Confirmed → Invalid
Revision history for this message
Ghanshyam Mann (ghanshyammann) wrote :

marking as invalid as this is more API change request which need spec than bug. feel free to propose the API spec for same.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.