post-config set after WSGI services are already started

[Radosław Piliszek]

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://lists.openstack.org/pipermail/openstack-discuss/2020-January/012152.html
[2] https://github.com/unbit/uwsgi/issues/1550

[Radosław Piliszek (yoctozepto)]

I changed the report to reflect the real issue at hand. Please ignore my previous comment.

[Radosław Piliszek (yoctozepto)]

The workaround is to simply restart API services after devstack is done deploying.

For example see: https://review.opendev.org/#/c/702132/24