cd2b8236e0
If an incoming request to placement does not set the accept header force it to 'application/json'. This not only ensures that error responses are in JSON but also that errors early in the middleware stack do not cause a key error (see the #1724065 bug). This fix is done by checking headers early in the middleware stack using the requestlog middleware as a convenient place to do the check. This overloads requestlog's purpose, but avoids adding yet more middleware (doing so has some small impact per request). Fixing bug 1724065 fixes a 500. Fixing bug 1674694 changes (for some requests) the content type of the bodies of 400-499 responses. This creates a bit of quandry for microversion handling. If a microversion is considered required here then it's not clear the global fix is worth doing and the 500 fix should be limited the microversion middleware. The intent all along has been that responses should strive to align with the API-WG errors guideline [1], which assumes application/json. [1] http://specs.openstack.org/openstack/api-wg/guidelines/errors.html Change-Id: Ice27c7080fc2df097cb387f7438c0aaf32b4c63d Closes-Bug: #1724065 Closes-Bug: #1674694
Team and repository tags
OpenStack Nova
OpenStack Nova provides a cloud computing fabric controller, supporting a wide variety of compute technologies, including: libvirt (KVM, Xen, LXC and more), Hyper-V, VMware, XenServer, OpenStack Ironic and PowerVM.
Use the following resources to learn more.
API
To learn how to use Nova's API, consult the documentation available online at:
For more information on OpenStack APIs, SDKs and CLIs in general, refer to:
Operators
To learn how to deploy and configure OpenStack Nova, consult the documentation available online at:
In the unfortunate event that bugs are discovered, they should be reported to the appropriate bug tracker. If you obtained the software from a 3rd party operating system vendor, it is often wise to use their own bug tracker for reporting problems. In all other cases use the master OpenStack bug tracker, available at:
Developers
For information on how to contribute to Nova, please see the contents of the CONTRIBUTING.rst.
Any new code must follow the development guidelines detailed in the HACKING.rst file, and pass all unit tests.
Further developer focused documentation is available at:
Other Information
During each Summit and Project Team Gathering, we agree on what the whole community wants to focus on for the upcoming release. The plans for nova can be found at: