yahoo-eng-team team mailing list archive

[hongbin <hongbin.lu@xxxxxxxxxx>]

Public bug reported:

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

** Affects: nova
     Importance: Undecided
         Status: New

** Description changed:

- 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.
+ 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

-- 
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):
  New

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