Previously, the stop_stack message accidentally used the
engine_life_check_timeout (by default, 2s). But unlike other messages sent
using that timeout, stop_stack needs to synchronously kill all running
threads operating on the stack. For a very large stack, this can easily
take much longer than a couple of seconds. This patch increases the timeout
to give a better chance of being able to start the delete.
Change-Id: I4b36ed7f1025b6439aeab63d71041bb2000363a0
Closes-Bug: #1499669
(cherry picked from commit e56fc689e19d92b5a3d23736d472c9a1fc698537)
Reviewed: https:/ /review. openstack. org/375469 /git.openstack. org/cgit/ openstack/ heat/commit/ ?id=ee86435e440 65f9d59425023b1 b8220826a6e0f2
Committed: https:/
Submitter: Jenkins
Branch: stable/newton
commit ee86435e44065f9 d59425023b1b822 0826a6e0f2
Author: Zane Bitter <email address hidden>
Date: Thu Sep 22 09:44:56 2016 -0400
Increase the timeout for the stop_stack message
Previously, the stop_stack message accidentally used the life_check_ timeout (by default, 2s). But unlike other messages sent
engine_
using that timeout, stop_stack needs to synchronously kill all running
threads operating on the stack. For a very large stack, this can easily
take much longer than a couple of seconds. This patch increases the timeout
to give a better chance of being able to start the delete.
Change-Id: I4b36ed7f1025b6 439aeab63d71041 bb2000363a0 5a3d23736d472c9 a1fc698537)
Closes-Bug: #1499669
(cherry picked from commit e56fc689e19d92b