post-config set after WSGI services are already started
Bug #1860287 reported by
Radosław Piliszek
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
devstack |
Triaged
|
Low
|
Unassigned |
Bug Description
This is a bug report to accompany my post to openstack-discuss mailing list [1].
Originally it concerned only CORS and blamed uWSGI (sorry!) but it turned out to be a false alarm [2].
The fact that at the moment it is impossible to make DevStack
use mod_wsgi except for keystone and placement holds but is irrelevant.
It turns out post-config is run after WSGI services are already started.
Hence all the trouble I experienced with uWSGI CORS.
mod_wsgi restarts apache2 for placement and hence reloads config (side effect).
[1] http://
[2] https:/
Changed in devstack: | |
status: | New → Triaged |
importance: | Undecided → Low |
To post a comment you must log in.
I changed the report to reflect the real issue at hand. Please ignore my previous comment.