I was able to reproduce this on devstack by using WSGI_MODE=mod_wsgi and playing with the processes value in the WSGIDaemonProcess apache setting. The number of times the warnings get emitted is related to the number of WSGI workers. If you have three or more workers, it will get pretty noisy, but it's still not as critical as I originally thought because it will still only happen a fixed number of times after the reload.
I was able to reproduce this on devstack by using WSGI_MODE=mod_wsgi and playing with the processes value in the WSGIDaemonProcess apache setting. The number of times the warnings get emitted is related to the number of WSGI workers. If you have three or more workers, it will get pretty noisy, but it's still not as critical as I originally thought because it will still only happen a fixed number of times after the reload.