cors.set_defaults does not have real test coverage in placement and probably not nova either
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
New
|
Undecided
|
Unassigned |
Bug Description
Both the placement and nova apis allow oslo_middleware
Placement has some gabbi functional tests which test that the middleware is present and does the right thing when using the middleware's own configuration defaults. Both when it is on or off in cors.yaml and non-cors.yaml.
However, the WSGI application that is actually used in a deployment, the one created by nova/api/
As far as I know, nothing (such as a tempest test) confirms those headers in either placement or nova, and it's relatively certain they are incomplete with regard to microversions (as OpenStack-
This bug is the result of discussion on https:/
The gabbi tests show the kinds of requests that can be done to confirm the right headers are generated: