When paunch removes a container, like applying a container's config
changes, it does that not gracefully. That poses an issue for some
cases, like stateful services. To mitigate that, attempt stopping the
container prior to removing it. And use the defined stop signal and
timeout settings for such a container, when stopping it. If there is no
signal/timeout in the config, fallback to deaults of SIGTERM and a 10s.
Reviewed: https:/ /review. openstack. org/630219 /git.openstack. org/cgit/ openstack/ paunch/ commit/ ?id=b5a14c6cd0b e76156852afdc8c 664e37e88bc7b3
Committed: https:/
Submitter: Zuul
Branch: master
commit b5a14c6cd0be761 56852afdc8c664e 37e88bc7b3
Author: Bogdan Dobrelya <email address hidden>
Date: Wed Jan 9 12:51:45 2019 +0200
Always attempt a graceful container stop/remove
When paunch removes a container, like applying a container's config
changes, it does that not gracefully. That poses an issue for some
cases, like stateful services. To mitigate that, attempt stopping the
container prior to removing it. And use the defined stop signal and
timeout settings for such a container, when stopping it. If there is no
signal/timeout in the config, fallback to deaults of SIGTERM and a 10s.
Related-bug: #1810690 5ff3ea7cea01969 3d61245212f
Change-Id: I7c72ea055984bb
Signed-off-by: Bogdan Dobrelya <email address hidden>