API: create operations should return 202
Bug #834013 reported by
Salvatore Orlando
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Won't Fix
|
Low
|
Salvatore Orlando | ||
quantum (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
API 'create' operations, according to the spec, should return HTTP status code 202.
They actually return HTTP status code 200.
This is due to the inability of the current wsgi framework to specify a status code when returning a non-empty response. Default HTTP status code is currently 200 (and that's the reason for which we get a 200 status code)
Related branches
lp:~salvatore-orlando/neutron/bug834013
- Brad Hall (community): Approve
- dan wendlandt: Approve
-
Diff: 125 lines (+33/-9)5 files modifiedquantum/api/api_common.py (+20/-0)
quantum/api/networks.py (+4/-2)
quantum/api/ports.py (+4/-1)
quantum/client.py (+1/-2)
tests/unit/test_api.py (+4/-4)
Changed in quantum: | |
assignee: | nobody → Salvatore Orlando (salvatore-orlando) |
importance: | Undecided → Low |
milestone: | none → diablo-rbp |
Changed in quantum: | |
status: | New → In Progress |
Changed in quantum: | |
status: | In Progress → Fix Committed |
Changed in quantum (Ubuntu): | |
status: | New → Fix Released |
To post a comment you must log in.
Reopening this bug as we had to revert the Fix for compatibility with the Quantum Manager in nova