Various extensions don't respect content header when returning a 202
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Undecided
|
Vish Ishaya |
Bug Description
Various nova extensions commands return a text response ("202 Accepted [..]") even when provided with an "Accept: application/json" header. For other 202 responses, either an empty body or a JSON-formatted response is standard. The implementation should be consistent with other 202's from Nova and other OpenStack Services.
This seems to be due to returning a webob exception instead of a response. The affected extensions are:
$ grep HTTPAccepted nova/api/
nova/api/
nova/api/
nova/api/
nova/api/
nova/api/
nova/api/
nova/api/
nova/api/
Changed in nova: | |
milestone: | none → juno-3 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | juno-3 → 2014.2 |
Fix proposed to branch: master /review. openstack. org/113668
Review: https:/