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
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1737338
Title:
Normal response code of addSecurityGroup is wrong
Status in OpenStack Compute (nova):
Invalid
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
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1737338/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
