commit 39918c82d3637f44be05615efc5c329f4acd16b3
Author: Eva Balycheva <email address hidden>
Date: Mon Oct 19 02:02:04 2015 +0300
Correctly stop uwsgi process during unstack.sh
When using Zaqar as plugin in DevStack, after executing unstack.sh,
there's still Zaqar uwsgi master process with it's workers running:
/usr/local/bin/uwsgi --ini /etc/zaqar/uwsgi.conf
This process must be stopped.
Also running uwsgi process will prevent Zaqar to start on the next
execution of stack.sh.
Reviewed: https:/ /review. openstack. org/236751 /git.openstack. org/cgit/ openstack/ zaqar/commit/ ?id=39918c82d36 37f44be05615efc 5c329f4acd16b3
Committed: https:/
Submitter: Jenkins
Branch: master
commit 39918c82d3637f4 4be05615efc5c32 9f4acd16b3
Author: Eva Balycheva <email address hidden>
Date: Mon Oct 19 02:02:04 2015 +0300
Correctly stop uwsgi process during unstack.sh
When using Zaqar as plugin in DevStack, after executing unstack.sh, local/bin/ uwsgi --ini /etc/zaqar/ uwsgi.conf
there's still Zaqar uwsgi master process with it's workers running:
/usr/
This process must be stopped.
Also running uwsgi process will prevent Zaqar to start on the next
execution of stack.sh.
The problem occurs, because of the nature of uwsgi container. /github. com/openstack/ zaqar/blob/ master/ devstack/ plugin. sh#L253
It just can't be stopped like that:
https:/
It must be stopped as described in uwsgi documentation: /uwsgi- docs.readthedoc s.org/en/ latest/ Management. html
https:/
This commit will make uwsgi container process stop correctly on
unstack.sh execution by using PID of the process as described in uwsgi
documentation.
Change-Id: I2f39ea5880c215 3fa14a8308d8710 969ef6a1a5e
Closes-Bug: 1504854